CoAgnes Labthe study spaceresearch preview · build 1ececa2

Where the machine grows · Volume 13

Volume 13 — Extension Specification: Experience Protocols (CoAgnes) and Learning (Nest Education)

SEEDsnapshot of 14 July 20266 min read← Volume 12 — Extension SpecificationVolume 14 — Conformance, Compatibility, and the Seven Verification Matrices →

Reading aids · CoAgnes LabNot part of the specification; where they differ, the volume governs.

At a glance

  • Position in the architecture, as the volume sets it out: CoAgnes purposes and cases require Nest runtime services and protocols; portable knowledge crosses the product boundary primarily as pipeline packages, not as code merges; CoAgnes needs drive runtime growth, and no capability is deemed universal because it can describe the runtime itself. §1
  • Two bootstrap capabilities: evidence-backed description, formed from inspectable sources, with CoAgnes and the runtime themselves as its first targets (the reflexive bootstrap); and pipeline authoring from reflection — the system proposes a reusable inert pipeline package, compiled, fixture-run, assessed, and promoted only after review. §2
  • A protocol vocabulary in candidate namespaces, whose first implementation stays on ordinary domain.fact rails under protocol rules carried over from the machine's discipline, and the seed semantic units: twelve knots (C0–C11) and nine binds (B0–B8), fixed as semantic obligations with technical projections. §3§4
  • Nest Education, a guided case canvas on the same machine: a learner steers an AI guide with a small vector grammar, and every gesture is a committed fact, never a direct graph mutation; both seeds converge on the same surface discipline, all views deriving from one wave log. §5§6
  • A bootstrap sequence in five tacts, from a self-description of the runtime to the trial internalised as Cells; the seed is viable when one user can traverse from Charter to a fresh application; and the blind spots it names, beginning with CoAgnes not yet grounded in the originating project. §7§8

Questions this volume answers

  1. How does portable knowledge cross the product boundary? §1
  2. What does the seed describe first, and can a description disagree with prose? §2
  3. Where do large bodies of evidence live, and what does the log carry? §3
  4. Can guide text satisfy a knot that requires human.answer? §5
  5. Does the learning surface need a change to the machine's core? §5
  6. When does a chat message become truth? §6
  7. When is the seed viable? §7
  8. What does the seed leave open? §8

Two seed extensions grow product surfaces on the machine without adding runtime capability of their own: CoAgnes experience authoring (evidence-backed description and description-to-pipeline authoring) and Nest Education (a guided learning canvasUnderstanding canvasSeveral clews winding in parallel and collecting one another's committed integrations through where clauses over lanes — cross-pollination under budgets. aka canvas. (Vol. 10 §4)Volume 15 — Terminology). Both are protocol-and-shell extensions in the sense of Vol. 11: new fact families, new derived readingsDerived readingAny view computed as a pure function of committed tuples and immutable artefacts — feed, trace digest (vault of lids), run metadata, extension digests. Shells hold no other truth. (Vol. 08 §8)Volume 15 — Terminology, new packages — same wave, same compiler, same assemblyAssemblyThe construction of one machine instance: engine with processors, membrane with controllers — one assembly shared by every shell of a product. (Vol. 08 §1)Volume 15 — Terminology, same membraneMembraneThe boundary where the wave meets the world: output controllers face outward, ingress faces inward. (Vol. 07)Volume 15 — Terminology. This volume is their complete statement within this set (lineage: the reference project's two conceptual seeds). Statements about CoAgnes remain design hypotheses until checked against the actual product; nothing here is an active contract.

§1. Position in the architecture

CoAgnes purposes and cases ──require──► Nest runtime services and protocols
        ▲                                        │ execute and record
        └────────── work surfaces ◄──────────────┘

Portable knowledge crosses the product boundary primarily as pipeline packagesPipeline packageA directory of pipeline.yaml beside schemas/* — the portable programme unit; drafts and templates are ordinary packages. (Vol. 09 §8)Volume 15 — Terminology (observed work → proposed YAML → compiler verdict → fixture and real runs → assessment and review → versioned library entry), not as code merges. The rule of growth: CoAgnes needs drive runtime growth; no capability is deemed universal because it can describe the runtime itself.

§2. The two bootstrap capabilities

  1. Evidence-backed description. A structured description — entities, responsibilities, boundaries, inputs/outputs/dependencies/effects, decisions, causal explanations, supporting and conflicting evidence references, unresolved questions, per-claim confidence, provenance — formed from inspectable sources. Its first targets are CoAgnes and the runtime themselves (reflexive bootstrap), and it must be able to disagree with prose where code or traces show a mismatch.
  2. Pipeline authoring from reflection. The system observes the method that produced a useful description and proposes a reusable inert pipeline packagePipeline packageA directory of pipeline.yaml beside schemas/* — the portable programme unit; drafts and templates are ordinary packages. (Vol. 09 §8)Volume 15 — Terminology — compiled by the existing loaderLoaderThe component that splits an authoring pipeline into individual records and commits them as seeds. aka splitter. (Vol. 09 §6)Volume 15 — Terminology, fixture-run, assessed, and promoted only after review. The Cell lifecycle (Vol. 12) later internalises the same cycle without changing its epistemic order.

§3. Protocol vocabulary (candidate namespaces)

First implementation stays on ordinary domain.fact rails (Vol. 04 §6 rules apply: closed shapes per authoritative publication, producer classes, collision review before canonical adoption):

experience.charter.requested        claim.proposed
evidence.source.declared            claim.challenged
evidence.registered                 description.candidate
evidence.access.failed              description.assessment.proposed
system.component.proposed           description.assessed
system.relation.proposed            pipeline.proposed        pipeline.compiled
system.map.described                pipeline.trial.completed pipeline.trial.rejected
                                    pipeline.reviewed
library.promotion.requested         library.entry.promoted

Protocol rules carried over from the machine's discipline: evidence is content-addressed — large bodies live in controller-owned stores; the log carries immutable references, digests, and bounded excerpts; every material claim cites committed evidence or shows an explicit gap; assessments follow the propose→normalise pattern of Vol. 12 §5.4 (the model never sets weights or aggregates); accepted publications are separate from candidates and carry provenance.

§4. Seed semantic units

The seed fixes twelve knotsActivation knotAn accumulating unit that matches wave tuples, winds them, and tests readiness; it accumulates understanding. When ready, it activates bind descriptors. Its minimal form is a single condition matcher — a degenerate configuration of the same accumulator, not a different kind. aka knot, clew (for the per-key instance see clew). (Vol. 05)Volume 15 — Terminology (C0–C11) and nine binds (B0–B8) as semantic obligations with technical projections. Digest:

UnitObligationProjection anchor
C0 Experience Charterfix what is described, why, criteria, ownercharter.proposed → charter.defined (or a validated input pre-CellSpace)
C1 Evidence substratematerial without collapsing source/interpretation/conclusionevidence.* facts; controller-owned stores
C2 System mapcomponents, responsibilities, relations before causal synthesissystem.* facts with closed schemas
C3 Claim & cause ledgerseparate observations, claims, hypotheses, contradictionsclaim facts; per-claim knots; independent evaluation
C4 Experience unitsmallest reusable piece of organisational experienceexperience.unit.* schemas; inert data
C5 Description integrationcoherent, source-linked descriptionoperator bind + gates → description.candidate
C6 Algorithmic reflectionwhich repeatable moves produced the resultpipeline.proposed (later a CellBlueprint) with semantic links
C7 Compiler/admission verdictplausible ≠ safely attemptablecompilePipeline, later admitCellPackage
C8 Trial & comparisonobserved behaviour before acceptanceisolated runs over the shared assembly; later Trial Cells
C9 Human decisionusefulness and capability stay humanreview facts; promotion distinct from acceptance
C10 Pipeline librarypreserve ways of working without universalising one tracepackage = pipeline.yaml + schemas/ + fixtures/ + manifest.yaml + evaluation.yaml + provenance.yaml
C11 Membrane capabilityevery external contact explicit and governablestatic controllers; capability panel

Binds B0–B8 wire these into the operating cycle: frame → register evidence → map → describe → reflect into algorithm → compile & trial → assess & decide → promote → instantiate a domain demonstration. Exact reuse only for declared templates; precedents inspire fresh authoring and cannot register topologyTopologyThe live set of registered activation knots and bind descriptors that the wave flows through. (Vol. 02 §5)Volume 15 — Terminology.

§5. Nest Education (learning surface)

The same machine carries a guided case canvasUnderstanding canvasSeveral clews winding in parallel and collecting one another's committed integrations through where clauses over lanes — cross-pollination under budgets. aka canvas. (Vol. 10 §4)Volume 15 — Terminology: a learner steers an AI guide with a small vector grammar; every gesture is a committed fact, never a direct graph mutation.

  • Vector grammar: deepen · connect · challenge · evidence · alternative · consequence · apply — each committed as learning.vector.given with a target reference and optional qualification; all input channels compile to the same fact shape (replayability, assessment, accessibility).
  • Case package: case.yaml + pipeline.yaml + schemas/ + evidence/ + rubric.yaml + views/ + fixtures/ + manifest.yaml — the executable centre is an ordinary pipeline; views/ optional, generic schema-derived UI always sufficient.
  • Authorship boundary (v1): every executable move is compiled before the session opens; a guide proposal carries an allowlisted move id; selection commits learning.bind.selected; bounded knotActivation knotAn accumulating unit that matches wave tuples, winds them, and tests readiness; it accumulates understanding. When ready, it activates bind descriptors. Its minimal form is a single condition matcher — a degenerate configuration of the same accumulator, not a different kind. aka knot, clew (for the per-key instance see clew). (Vol. 05)Volume 15 — Terminology authorship rides the existing unfoldUnfoldThe constrained in-wave authoring form: a service result instantiates declared knot/close/head templates. (Vol. 06 §7)Volume 15 — Terminology template; genuinely new topologyTopologyThe live set of registered activation knots and bind descriptors that the wave flows through. (Vol. 02 §5)Volume 15 — Terminology becomes an inert draft → compile → separate trial run (later a Trial Cell). Knots requiring human.answer cannot be satisfied by guide text.
  • Actors: learner (judgement), guide (proposals only), independent evaluator (rubric fixed before the run; deterministic normalisation), case author, platform operator (control plane).
  • Derived states (proposed → open → winding → ready → integrated, with disputed/awaiting_human) are read-model language over facts, readinessReadinessThe state an activation knot reaches when its accumulated understanding satisfies its test; readiness is what activates bind descriptors. Readiness is reified: the topology commits it as a tuple carrying the understanding snapshot. (Vol. 02 §5, Vol. 04 §2.3)Volume 15 — Terminology, and unanswered intentions — no UI-private state.
  • Infrastructure prerequisite: multi-turn ingressIngressThe inward half of the membrane: the edge through which external events — the world's answers among them — are committed to the wave log as fact tuples. (Vol. 07 §6)Volume 15 — Terminology = the WaveSession layer (Vol. 12 §8); the education seed adds no core change.

§6. Work surfaces

Both seeds converge on the same surface discipline (Vol. 08 §8): a Charter/ obligation rail; a document-first centre (description, map, algorithm, trial comparison, trace); an evidence/decision panel answering what supports this, what contradicts it, what did it cost, what may I decide now; chat as a narrow ingressIngressThe inward half of the membrane: the edge through which external events — the world's answers among them — are committed to the wave log as fact tuples. (Vol. 07 §6)Volume 15 — Terminology lane whose messages become truth only as committed facts; Studio depth (vault, feed, bricks, YAML) always reachable. All views derive from one wave logWave logThe ordered, append-only history of committed wave tuples. The single source of truth; entries are never rewritten, only appended. aka append-log. (Vol. 03)Volume 15 — Terminology.

§7. Bootstrap sequence and acceptance

Tact 1 — self-description of the runtime from this repository (every material claim evidenced or gapped; reconstructable from references and the run log). Tact 2 — reflection proposes the pipeline that could repeat Tact 1; compiled, fixture-run, promoted only through review. Tact 3 — describe CoAgnes with the real corpus; incompatibilities become requirements or applicability limits, never silent prompt edits. Tact 4 — first external domain demo with an expert reviewer. Tact 5 — internalise the trial as Cells (Vol. 12) with identical Charter/evidence/assessment/review contracts and root-only compatibility.

Lab fig. 13·1Five dashed stops along one dashed line, Tact 1 to Tact 5, each with its words: self-description of the runtime, every material claim evidenced or gapped; reflection proposes the pipeline, promoted only through review; describe CoAgnes with the real corpus; first external domain demo with an expert reviewer; internalise the trial as Cells. A dashed arc runs back from Tact 2 to Tact 1, marked could repeat Tact 1. A legend: dashed, a seed.Bootstrap sequencecould repeat Tact 1Tact 1self-descriptionof the runtimeevery materialclaim evidencedor gappedTact 2reflection proposesthe pipelinecompiled, fixture-run,promoted onlythrough reviewTact 3describe CoAgneswith the real corpusincompatibilitiesbecome requirementsor applicabilitylimits, never silentprompt editsTact 4first externaldomain demowith an expertreviewerTact 5internalise the trialas Cells (Vol. 12)with identical Charter/evidence/assessment/review contracts androot-only compatibilitydashed — a seed: nothing here is an active contract
Lab fig. 13·1Five dashed stops along one dashed line, Tact 1 to Tact 5, each with its words: self-description of the runtime, every material claim evidenced or gapped; reflection proposes the pipeline, promoted only through review; describe CoAgnes with the real corpus; first external domain demo with an expert reviewer; internalise the trial as Cells. A dashed arc runs back from Tact 2 to Tact 1, marked could repeat Tact 1. A legend: dashed, a seed.Bootstrap sequenceTact 1self-description of the runtimeevery material claim evidenced or gappedTact 2reflection proposes the pipelinethat could repeat Tact 1compiled, fixture-run, promoted onlythrough reviewTact 3describe CoAgnes with the real corpusincompatibilities become requirementsor applicability limits, never silentprompt editsTact 4first external domain demowith an expert reviewerTact 5internalise the trial as Cells (Vol. 12)with identical Charter/evidence/assessment/review contracts androot-only compatibilitydashed — a seed: nothing here is an active contract
Lab fig. 13·1 The bootstrap sequence the seed sets out, in five tacts: a self-description of the runtime, every material claim evidenced or gapped; reflection proposing the pipeline that could repeat Tact 1, promoted only through review; CoAgnes described with the real corpus; a first external domain demo with an expert reviewer; the trial internalised as Cells (Vol. 12). Drawn dashed: the volume is a seed, and nothing here is an active contract. A reading aid by CoAgnes Lab; §7 governs.
Lab fig. 13·2Eleven dashed stops along one dashed line: Charter, evidence, map/ledger, description, pipeline proposal, compiler verdict, trial, independent assessment, human decision, promoted package, fresh application. A bracket spans every stop and leads to five questions to answer at every step: what was committed, why the next operation was allowed, which evidence supports the result, which capability crossed the membrane, which exact package was accepted. A legend: dashed, a seed.The seed is viable when one user can traverseCharterevidencemap/ledgerdescriptionpipelineproposalcompilerverdicttrialindependentassessmenthumandecisionpromotedpackagefreshapplicationAt every step, answerwhat was committedwhy the next operation was allowedwhich evidence supports the resultwhich capability crossed the membranewhich exact package was accepteddashed — a seed: nothing here is an active contract
Lab fig. 13·2Eleven dashed stops along one dashed line: Charter, evidence, map/ledger, description, pipeline proposal, compiler verdict, trial, independent assessment, human decision, promoted package, fresh application. A bracket spans every stop and leads to five questions to answer at every step: what was committed, why the next operation was allowed, which evidence supports the result, which capability crossed the membrane, which exact package was accepted. A legend: dashed, a seed.The seed is viable whenone user can traverseCharterevidencemap/ledgerdescriptionpipeline proposalcompiler verdicttrialindependent assessmenthuman decisionpromoted packagefresh applicationAt every step, answerwhat was committedwhy the next operation was allowedwhich evidence supports the resultwhich capability crossed the membranewhich exact package was accepteddashed — a seed: nothing here is an active contract
Lab fig. 13·2 The seed is viable when one user can traverse from Charter to a fresh application — through evidence, map/ledger, description, pipeline proposal, compiler verdict, trial, independent assessment, human decision and promoted package — and at every step answer what was committed, why the next operation was allowed, which evidence supports the result, which capability crossed the membrane, and which exact package was accepted. Drawn dashed, like the whole volume: nothing here is an active contract. A reading aid by CoAgnes Lab; §7 governs.

The seed is viable when one user can traverse: Charter → evidence → map/ledger → description → pipeline proposal → compiler verdict → trial → independent assessment → human decision → promoted package → fresh application — and at every step answer what was committed, why the next operation was allowed, which evidence supports the result, which capability crossed the membraneMembraneThe boundary where the wave meets the world: output controllers face outward, ingress faces inward. (Vol. 07)Volume 15 — Terminology, and which exact package was accepted.

§8. Blind spots

CoAgnes is not yet grounded in the originating project (no canonical source or domain contract was available when the seed was written); reflexive confirmation risk (descriptions that agree with their own vocabulary — mandatory source references, contradiction knotsActivation knotAn accumulating unit that matches wave tuples, winds them, and tests readiness; it accumulates understanding. When ready, it activates bind descriptors. Its minimal form is a single condition matcher — a degenerate configuration of the same accumulator, not a different kind. aka knot, clew (for the per-key instance see clew). (Vol. 05)Volume 15 — Terminology, independent review); evidence access/privacy (identity, tenancy, retention, redaction, consent); causal overstatement (alternatives and uncertainty stay first-class); pipeline overfitting (applicability manifests and failure examples before reuse); authoring-schema limits (compiler expansion follows observed needs, explicit rejection retained); restart/durable sessions (Vol. 11 §6.1); evaluation independence; library governance (deprecation, migration, licences, responsibility); work-surface density (Charter/document/decision first, technical depth on demandDemandA named binding (as:) to an activation knot whose integrated understanding the bind descriptor gathers back. The gathering face of affinity, and the second method through which understanding enters the bind. aka tendril. (Vol. 06 §3–4)Volume 15 — Terminology). For the learning surface additionally: rubric visibility policy, learner privacy, and the gap that today's run orchestration owns a runtime for a single settleSettleThe runtime algorithm alternating propagation with membrane discharges until the machine settles. (Vol. 08 §3)Volume 15 — Terminology only.