Skip to content

🔧 chore: specs and changes live in the central OpenSpec store - #24

Open
edgarmesquita wants to merge 3 commits into
masterfrom
chore/openspec-central-store
Open

edgarmesquita wants to merge 3 commits into
masterfrom
chore/openspec-central-store

Conversation

@edgarmesquita

Copy link
Copy Markdown
Contributor

Part of eQuantic/equantic-specs#1... every eQuantic product now plans in one OpenSpec store, with the specs grouped by workstream. This repo's workstream is core.

This PR only connects the repo to it. openspec/config.yaml is a one-line pointer (store: equantic-specs), so /opsx:propose, /opsx:apply and the openspec CLI run here act on the store.

openspec init added the /opsx commands and skills for that pointer, .claude/settings.json lets a session write to ../equantic-specs, and CLAUDE.md says where the specs are.

No code changes. openspec doctor run on this branch resolves to the store.

openspec/config.yaml points at eQuantic/equantic-specs, where every eQuantic product keeps its
specs by workstream; this repository's is `core`. `openspec init` installed the /opsx commands
and skills for that pointer, the project settings let a session write to ../equantic-specs, and
CLAUDE.md says where the specs are.
…ame the change

A machine without the store found nothing here to set it up, and an apply with no name could pick
another workstream's change, since the store holds every product's. Part of
eQuantic/equantic-specs#1, and eQuantic/equantic-specs#2 tracks enforcing the second.
The pointer, CLAUDE.md and the ledger said this repository's specs and changes both live under
openspec/specs/<workstream>/. Only the specs do: the changes live under openspec/changes/, each named
after the workstream. Copilot caught it in eQuantic/equantic-subscription-api#130.
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown

Code Coverage

Package Line Rate Branch Rate Health
eQuantic.Core 13% 12% ❌
eQuantic.Core.Eventing.Kafka 36% 20% ❌
eQuantic.Core.Eventing.RabbitMQ 37% 13% ❌
eQuantic.Core.Eventing 11% 0% ❌
eQuantic.Core.Eventing.Outbox 45% 19% ❌
Summary 24% (355 / 1781) 13% (101 / 801) ❌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants