Skip to content

docs: JFA conformance self-description + dependency-leaf CI#6

Merged
NetworkTheoryAppliedResearchInstitute merged 2 commits into
mainfrom
docs/jfa-conformance
Jul 13, 2026
Merged

docs: JFA conformance self-description + dependency-leaf CI#6
NetworkTheoryAppliedResearchInstitute merged 2 commits into
mainfrom
docs/jfa-conformance

Conversation

@NetworkTheoryAppliedResearchInstitute

Copy link
Copy Markdown
Contributor

What this adds

Per the legibility rule adopted for all NTARI repos — each program describes itself in the architecture's role language before anything product-specific — this PR makes sohocloud-protocol the template:

  • CONFORMANCE.md — role declaration (substrate coordination protocol, dependency leaf), a term-mapping table (Node/Coordinator/Frontend ↔ architecture roles), and an invariant table where every claim is bound to the mechanism and check that enforces it. Stand-ins are named per the architecture's honesty rule (anchor stub, v0 UNSTABLE, mechanical-not-economic exit).
  • CLAUDE.md — the layer invariants and change discipline for agent-assisted work: SPEC-first, every normative MUST gets a check, wire change = version bump + regenerated vectors, author never merges own PR, refuse-or-flag list, tension protocol.
  • .github/workflows/dependency-leaf.yml — the dependency-leaf invariant as CI: any go.mod requirement fails the build. (Named distinctly from the CI in ci: Go build/vet/test + Python conformance gate #4; no conflict — merge order does not matter.)

No code changes; no wire changes. All conformance claims were verified against main before writing (zero-dep go.mod, vectors.json + reproduce_spec.py + golden test present).

🤖 Generated with Claude Code

Role-first self-description per the architecture's legibility rule:
CONFORMANCE.md declares the module's JFA role (substrate coordination
protocol, dependency leaf) and binds every conformance claim to the
mechanism and check that enforces it, with stand-ins named. CLAUDE.md
carries the layer invariants and change discipline (SPEC-first, every
MUST gets a check, wire change = version bump). The dependency-leaf CI
workflow turns the leaf invariant into a failed build instead of a
review catch.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@NetworkTheoryAppliedResearchInstitute
NetworkTheoryAppliedResearchInstitute merged commit e37d39d into main Jul 13, 2026
3 checks passed
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.

1 participant