Feedback & State
Atomic primitives in the feedback & state family. Click any tile for the live render, the spec it was built from, and the code that fell out.
Spec Linted
SPEC-042 passed all gates. ICS score: 78.
Governance · Breach
Merge bypassed gate
PR #482 merged without GO sign-off. Reconcile or revert before next release.
Run spec_linter before scoring — gate 1 must pass first.
Gate cleared
SPEC-038 passed ICS gate 2
ICS score 84. Promoted to STABLE. Ready for handoff.
Heads up
Threat model stale by 14 days
SPEC-014 ships in 3 days. Re-run threat-validator before the freeze.
P0 · INC-0421
Critical: governance breach
auth/session-mint — session secret rotated without spec update.
ICS scorer now reads spec.yaml
Frontmatter-only specs still work. Mixed-mode is reported as a warning.
POST /v1/specs/score retires on 2026-07-01
Migrate to POST /v2/specs/score. Same payload, stricter validation.
Scheduled window
reconciliation-engine · read-only
2026-05-24 02:00 → 2026-05-24 04:00. Writes queue and replay on resume.
POL-014 · effective 2026-06-01
Review quorum updated
every PR over 200 lines requires two GO reviewers.
Spec saved
SPEC-038 · v1.4
Gate 1 failed
Missing acceptance criteria block
ICS score 58 falls below the gate threshold of 60.
New compendium category
feedback-state now hosts 13 alert atoms. Filter from the sidebar.
Next step
Three specs are ready for handoff
ICS scores above 80. CO reviewers have signed. The DE board is waiting.
ICS score below threshold
SPEC-042 scored 47 against a minimum of 60. Acceptance criteria are under-specified.
SPEC-118 / ics-recompute
Threshold-rescore batch entered the worker queue at 14:02:11. Lease pool size is 4. ETA depends on neighbour load.
Step 3 of 5 · Threat validation
since 14:02:11Holds lease until 14:05:00
SPEC-204 / quota-allocator
Linter, ICS scorer, and threat validator all returned clean. Awaiting governance handle to advance the artefact to APPROVED.
Waits on SPEC-118
Threshold rescore cannot proceed until upstream spec lands. Owner: @governor
SPEC-031 / legacy-quota
Superseded by SPEC-204 in 2026-04. Retained read-only for lineage queries and after-action review.
TOOL-007 / metrics-legacy
End-of-life on 2026-05-15. No successor — the underlying use case dissolved when ICS scoring went inline. Read-only.
SPEC-077 / lineage-card
Signature on the last revision does not match the recorded committer key. Access restricted until a governance handle clears or rejects.
SPEC-204 / quota-allocator
Acceptance criteria revised in the last build window. Spec reflects current intent — downstream tools may consume.
SPEC-042 / threat-profile
Last validated 47 days ago. The 30-day freshness window has lapsed — re-run the gate suite before downstream consumption.
SPEC-061 / tenant-isolation
Owner handle field is empty. Surfaced by the ownership audit sweep; governance must assign a responsible handle before the next gate can advance the artefact.
Linting SPEC-042 · gate 2 of 3
// nothing here yet
No specs on stage
Intent is the primary artefact. Author the first spec to raise the curtain.
+Author Spec// 0 rows
List is empty
No specs have been authored on this stream yet. Author one to begin.
Author first spec// 0 matches
Nothing matches that query
Try shorter terms, drop a filter, or check the corpus is loaded.
No corpus yet
The ledger is open. The first spec is the first commit.
- 0Specs
- 0Threats
- 0Runbooks
// nothing matches
Try removing a filter
Three steps to your first ship
- 1 AUTHORWrite intent, criteria, constraints, failure modes.
- 2 GATERun spec-linter and ics-scorer; clear threshold 60.
- 3 SHIPCompose with AI, govern with humans, ship the artefact.
Saving spec
gate 2 of 3 · ics-scorer
Spec ledger
SPEC-014 · SPEC-029 · SPEC-038 · SPEC-052
- approved · 4
- draft · 2
- review · 1
- retired · 0
// please wait
Reconciling corpus
Fetching more
// upstream · spec-registry
Could not reach registry
The corpus service responded 503. The last good snapshot was 3 minutes ago.
// no live data
Showing cached snapshot
Last synced 2026-05-21 08:42. Edits will queue and replay when the link returns.
// requires role
governor · read
Granted by the security-lead role. Your request will appear on their inbox.
// not built yet
Coming next quarter
Multi-agent fleet status will ship on the v0.4 milestone. Subscribe to be told when.
// destructive
Delete SPEC-042?
This spec has 3 downstream artefacts. Deletion is permanent — supersede instead if you intend to preserve lineage.
Type SPEC-042/auth.session to enable deletion.
Apply 4 spec changes?
3 downstream artefacts will be regenerated. Estimated build time ~42s.
- · SPEC-038 · session.ttl
- · SPEC-041 · auth.scope
Force-roll auth keys
This action will execute even if reviewers are mid-flight. The following effects are immediate:
- 01 3 downstream specs will be unlinked
- 02 Active sessions (~1,240) will be terminated
- 03 Replay buffer for 24h will be purged
Once you confirm, the artefact is purged from cold storage. No backup, no replay, no admin override.
- @governor signed
- @spec-owner signed
- @security-lead pending
- @platform-lead pending
GO-09 / Retention
The role below has read this policy in full and accepted it as a binding constraint on subsequent actions.
- ts
- 2026-05-22T09:14Z
- by
- @spec-owner
Receipt for SPEC-038 migration approval. Verifiable in the governance log.
Confirmation will arm in 3 seconds. Stay on this view to cancel.
Enter the 6-digit code from your authenticator app.
You asked to rotate auth keys. That action requires approval from the role above.
- elapsed
- 12m
- target
- same business day
SPEC-041 draft has unsaved edits. Leaving now drops them.
The framework is real.
The community is forming now.
DoCoDeGo is in Alpha. The framework is documented, the practices are battle-tested at small scale, and the next release is being shaped in public.
If it produces anything, it should produce engineers and teams who think more clearly about what they are building and why.
Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.