outcomeA boundary for assistant-written presentation
spec:consumers.ai-assisted-readingNew since the base graph base b5e0a8b. See the diff.
Base input: schema 0.12.0, 456 Specs.
Next rung scoped waits on 1 unmet clause:
kind-evidence-present· The kind's natural evidence is present (per-kind evidence table).
Packs: pack:self-hosting-v1
Design: no design entries · no pinned declarations · no decisions
Findings: no errors, no warnings
specs/consumers/ai-assisted-reading.sdp.md
1 open question and 1 blocking question; implementation binding none, verifier binding none, and expected-outcome oracle none.
Every reading the Protocol ships is a deterministic function of the graph and the inputs a caller names, as founding principle P3, deterministic derivation, requires. An assistant that only selects one of those readings keeps that property; one that writes explanations or arrangements of its own does not, so its output needs a contract before it reaches a reader.
Intent
- Let a reader ask for a useful existing reading and inspect why it was selected and what scope it omits.
Open questions
- blocking ·
question.aiPresentationBoundaryline 27 · specs/consumers/ai-assisted-reading.sdp.md:27· If an assistant generates explanations or arrangements beyond selecting deterministic readings, what contract keeps its output distinct from graph claims and makes the exact reading reviewable, including how the exact output is retained with its model, prompt and inputs?Decider: ownerLinks: spec:consumers.projections-model, spec:extraction.claim-taxonomy, spec:decisions.shipped-projections-frozen, spec:consumers.spec-studio#rule.namedInputsProvisional: Select existing deterministic readings only; any generated text stays outside the Studio and the frozen projections, labelled as assistant output with its source commit and scope, and adds no claim, fact or validator.Trigger: the UX design pass measures that assistant selection or a generated explanation helps a named review task
Behavior
0 unkeyed rules.
Verification
Verifier bindings
No verifier binding recorded.
Design view
Requirement drawing
- Declared verifying examples: no declared verifying example.
- Satisfying or referencing units: no recorded binding.
- Test or oracle bindings: no recorded binding.
Arrows: refines (declared).
The diagram as text
- spec:consumers.ai-assisted-reading: A boundary for assistant-written presentation · declared Spec · no satisfying binding
- spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores · declared Spec
- spec:consumers.ai-assisted-reading refines spec:consumers.projections-model · declared — the boundary is drawn against the projection law, a pure function of the graph
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.
Decisions
No decision record named.
Runtime
No implementation neighborhood recorded.
Runtime observation: not tracked.
Evidence
Runtime observation: not tracked.
Build attestations: not tracked.
Deployments: not tracked.
Bills of materials: not tracked.
Impact
The diagram as text
- spec:consumers.ai-assisted-reading: A boundary for assistant-written presentation
- spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores
- spec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph
- spec:decisions.shipped-projections-frozen: The shipped projections stay frozen
- spec:extraction.claim-taxonomy: Graph claims retain their epistemic source
- spec:consumers.ai-assisted-reading dependsOn spec:consumers.spec-studio · declared — the Studio reads only the graph and its named inputs
- spec:consumers.ai-assisted-reading dependsOn spec:decisions.shipped-projections-frozen · declared — the shipped projections stay frozen
- spec:consumers.ai-assisted-reading dependsOn spec:extraction.claim-taxonomy · declared — each graph claim carries one of the three claim categories
- spec:consumers.ai-assisted-reading refines spec:consumers.projections-model · declared — the boundary is drawn against the projection law, a pure function of the graph
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.
Rests on
- refines · spec:consumers.projections-model · stated ready, floor ready
- dependsOn · spec:consumers.spec-studio · stated ready, floor ready
- dependsOn · spec:decisions.shipped-projections-frozen · stated ready, floor ready
- dependsOn · spec:extraction.claim-taxonomy · stated ready, floor ready
Rested on by
No Spec rests on this Spec.
Relations
| Relation and direction | Other end | Claim | Reason | Exercised keys |
|---|---|---|---|---|
| dependsOn · outgoing | The Spec Studio is a static HTML workbench over the one graphspec:consumers.spec-studio · resolves | declared | the Studio reads only the graph and its named inputs | None |
| dependsOn · outgoing | The shipped projections stay frozenspec:decisions.shipped-projections-frozen · resolves | declared | the shipped projections stay frozen | None |
| dependsOn · outgoing | Graph claims retain their epistemic sourcespec:extraction.claim-taxonomy · resolves | declared | each graph claim carries one of the three claim categories | None |
| refines · outgoing | Projections fan out from one graph without becoming truth storesspec:consumers.projections-model · resolves | declared | the boundary is drawn against the projection law, a pure function of the graph | None |
Bindings
Implementation binding: none
Design reference: none
Verifier binding: none
Expected-outcome oracle: none
Runtime observation: not tracked.
Run results: not recorded in the graph.
Findings
None.
Composing (0)
Composing needs the script.