Skip to content

docs: CSD/4 (topology-declared fixtures) — client-side executability evaluation - #135

Merged
emooreatx merged 1 commit into
mainfrom
docs/csd4-evaluation
Sep 29, 2026
Merged

emooreatx merged 1 commit into
mainfrom
docs/csd4-evaluation

Conversation

@emooreatx

Copy link
Copy Markdown
Contributor

Answers the CIRISServer session's five questions on CSD/4 = CSD/3 + topology: (typed by CIRISServer FSD/TOPOLOGY.md) + per-layer checks:, with file:line on both sides. Summary in CIRISClient#134.

  1. Executable as-is: partly. The harness builder's values.json is already our ${NAME} shape, so the client-UI layer runs today behind a server_harness fixture; roots/persons/nodes/relations run in the harness but not on the matrix (legs download the released binary; the synthetic root is test-anchor only); no --attach mode exists yet; the agent layer has no vocabulary.
  2. Gate testable on topology coverage: a csd:topology block, checked layer-by-layer against a checked-in per-fixture declaration, with a failure message naming layer and row.
  3. Native test-anchor per host target (three binaries, not five); doesn't fit the iOS actor node (embedded released node) or Windows until the harness gets process-group handling.
  4. Vocabulary gaps for households/communities (held quorum changes, late members), moderation (delegation chains), accord/duty conferral, trust-root cards, and pre:/post: for cards that create state; draft blocks per card.
  5. Traceability: a red carries layer, CC clause, CEG dimension, tag and the harness's log evidence; what flow_spec and the CSD need to carry it.

Ten concrete server asks (§6) and the client plan by file (§7).

🤖 Generated with Claude Code

https://claude.ai/code/session_0155SkTGdbwnSnR6tWBqJvUM

…cutability

FSD/CSD4_EVALUATION.md answers, per layer and with file:line citations on
both sides (CIRISServer chore/adopt-edge-v33 @ 7c13f96f harness/native +
FSD/TOPOLOGY.md; this repo's flow runner, two_node fixture, check_csd_v3
and the five-platform workflow): whether the runner can execute CSD/4
as-is, how check_csd_v3 should gate `testable` on topology coverage, where
a native test-anchor ciris-server fits the five-platform matrix, which
CSDs need layers the vocabulary lacks (with draft topology blocks), and
what a red must carry to name the layer and the CC clause. Ends with the
concrete asks of the server and the client's plan by file.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0155SkTGdbwnSnR6tWBqJvUM
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@emooreatx
emooreatx merged commit 64d5d68 into main Sep 29, 2026
5 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