A family specification package, distributed free of charge. It defines the normative boundary and decision logic of the SSCAR family: its component agents, its family integrator, and the composed family-level verdict that none of the components produces alone.
When you copy your work into the next session, the words come with you. The thinking does not.
What is lost in the copy is not content. The content transferred. What is lost is everything about the content that gave the work its shape.
This is what we mean by epistemic continuity: not the content of the work, but the structure of the thinking — what is settled, what is open, what is provisional, what is owed, what came from where.
The copy carried the words. It did not carry the work.
This package is a self-contained, normative, execution-neutral family specification, delivered as-is, sufficient for an engineering team to build the family — each component agent and the integrator that composes them — without further design decisions about agent logic, composition order, evidence shape, validator behavior, or failure semantics.
This package is not software, SaaS, a managed service, consulting, support, managed operations, or implementation delivery. It is not a live runtime — nothing in the package executes; everything in the package describes how a conforming executable family must behave.
The family capability is emergent: it arises only from the complete composition of all component agents together with the integrator and its connector annexes. No component produces it alone, and no subset of components produces it.
6 structural properties, defined in spec §17.3 Stable semantic core and elaborated through the failure semantics, workflow, gate logic, and evidence contract sections:
Family verdict vocabulary and disclosure classes remain fixed.
Contamination definition and fail-closed behavior remain fixed.
Strict monotonic anchor requirement and accepted-head linkage remain fixed.
Verified rehydration precedes semantic replay.
Replay sufficiency and offline reconstructibility remain required.
Disclosure-class preservation and evidence closure remain required.
These are properties of the specification. They are not warranties about a delivered running system.
| UNIT/AGT-VRA-001/ | Verified Rehydration Agent — component agent. Its own specification, indexes, ambiguity register and conformance tests, with its own README, Whitepaper, License and Manifest. |
| UNIT/FPA-FRESHNESS-PORTABILITY-003/ | Freshness Portability Agent — component agent. Its own specification, indexes, ambiguity register and conformance tests, with its own README, Whitepaper, License and Manifest. |
| UNIT/BDA-BOUNDARY-DEFENSE-002/ | Boundary Defense Agent — component agent. Its own specification, indexes, ambiguity register and conformance tests, with its own README, Whitepaper, License and Manifest. |
| UNIT/TAA-TRUTH-ARBITRATION-001/ | Truth Arbitration Agent — component agent. Its own specification, indexes, ambiguity register and conformance tests, with its own README, Whitepaper, License and Manifest. |
| UNIT/ARA-AUDIT-REPLAY-001/ | Audit Replay Agent — component agent. Its own specification, indexes, ambiguity register and conformance tests, with its own README, Whitepaper, License and Manifest. |
| UNIT/FAM-SSCAR-FI-001/ | Session State Continuity & Anchor Replay Family Integrator — family integrator. Its own specification, indexes, ambiguity register and conformance tests, with its own README, Whitepaper and Manifest. It additionally carries the connector annexes (SSCAR_Concept_Identity_Register.md, SSCAR_Family_Connector_Tests.md, SSCAR_Producer_Consumer_Manifest.md), which define what each component exposes to the composition and what the composition may assume. No component carries these. |
| NNT_Family_Companion/ | Non-Normative Tests for the composed family. Demonstration-only evidence that the family is derivable; not a reference implementation, and not part of the specification. |
| SSCAR_Family_README.md | The package's map: what is in it and how the pieces relate. |
| SSCAR_Family_License.md | The license for this family package. |
| SSCAR_Family_Manifest.sha256 | Family-level SHA-256 manifest: each unit's own Manifest, direct hashes of the unit files those Manifests do not cover, and the family-level files. Two-level integrity. |
| verify.md | Self-audit runbook you run against the package you hold. |
The component specifications in this package are the same normative documents distributed as standalone agent packages. What this package adds is the integrator, the connector annexes, and the composed conformance suite — that is, the family-level guarantee.
Implementing the components without the integrator produces conforming components and no family. Implementing the integrator against components that do not pass their own conformance suites produces a composition with no foundation. Neither is a conforming family, and neither carries the family-level verdict.
Per spec §17 Implementation Boundaries, Optional Parameters, and Reuse Rules and §16 Acceptance Criteria, 6 deployment artifacts your engineering team builds from this specification:
A conforming executable family integrator implementing the workflow states, validator catalogue, decision table, gate logic, and fail-closed verdict emission.
Component wiring and adapters for Audit Replay Agent (ARA), Boundary Defense Agent (BDA), Freshness Portability Agent (FPA), Truth Arbitration Agent (TAA), and Verified Rehydration Agent (VRA), using Annex A producer-consumer wiring and Annex B canonical-token identity rules.
Boundary intake, replay-request, readmission-review, and output projections for FIC-01 through FIC-03 and FOC-01 through FOC-05.
An evidence assembly and export pipeline producing FEV-01 through FEV-15, including BoundaryEventEvidenceReport, report_signature, and export_manifest_ref.
An operator-declared implementation profile covering cryptographic suite, storage backend, serialization, operator workflow, optional assurance and attestation controls, and any downstream rollback action.
A conformance harness and release-acceptance record running the public test suite and all Annex C connector tests.
The specification is complete enough that none of these requires interpretation of ambiguous prose. Spec §16 AC-01 through AC-08 set the acceptance criteria your implementation must meet.
The integrator has a single deployment scope: a high-audit continuity environment with offline replay, cross-session handoff, and possible model change. It is implemented and operated by your engineering and operations teams as a normative-critical family integrator that composes local component outcomes into a fail-closed family replay-admissibility verdict and an offline-reconstructible boundary-event evidence report.
The integrator is delivered only in the Family Pack alongside the 5 component agent specifications and the three operational connector annexes.
In all cases, deployment is performed by your engineering and operations teams. This package is not the deployer.
The integrator has finite, fail-closed authority over boundary cleanliness, carried-claim provenance admissibility, accepted-head and anchor validation, verified rehydration closure, replay continuity and admissibility, and boundary-event evidence reporting. It may compose local outcomes into a family verdict, validate cross-domain closure, block family replay, open hold and readmission review, and issue a boundary-event evidence report. It may not classify external truth, issue policy overrides, approve tool-state, execute restore, move continuity watermarks, substitute local validators, or rewrite accepted history.
This boundary is normative (spec §2 and §16 AC-08) and cannot be overridden by integration choices.
This runbook has you establish, on the package you hold and on your own machine, that you received what was promised. It does so at three levels:
Each check has the same shape: find what the package declares, observe what your machine produces, record whether they match.
Integrity check, run inside the unzipped package folder.
sha256sum -c SSCAR_Family_Manifest.sha256
shasum -a 256 -c SSCAR_Family_Manifest.sha256
Get-Content SSCAR_Family_Manifest.sha256 | ? { $_ -notmatch '^\s*#' -and $_.Trim() } | % { $h,$f = $_ -split '\s+',2; if ((Get-FileHash $f.Trim() -Algorithm SHA256).Hash -ieq $h) { "OK $f" } else { "FAIL $f" } }Recompute the Family Manifest's own hash and compare it to the manifest_ref bound in the License.
The Conformance Tests document contains 28 test records anchored 1:1 to the specification: 19 directly runnable on the integrator's projection surface, 2 parameterized against operator-declared inputs, and 7 declarative checks verified at integration level. Each record cites the specification authority that grounds it, the input fixture that drives it, and the oracle that defines pass and fail. The Minimal Run Note declares the projection surface, input types, assertion result types, and the conformance condition for the suite as a whole.
Run the suite against your implementation. A fully conformant implementation passes the 19 runnable tests, satisfies the 2 parameterized tests under your declared parameter envelopes, and attests the 7 declarative checks at your release-acceptance gate.
In addition, Annex C contains 14 wiring tests you run that verify correct connection of components to the integrator at the family layer. Each wiring test declares its input surface, execution surface, assertion set, PASS condition, and forbidden semantic collapse. A fully conformant family implementation passes the integrator's Conformance Tests (above) AND all 14 wiring tests in Annex C. Failure at either level is a family conformance failure.
Your implementation's conformance is established by the Conformance Tests, not by verify.md.
Five paradigm-isolated reconstruction contexts of the same model independently built the Session State Continuity & Anchor Replay Family from the specification pack alone — in Python, Rust, Prolog, C, and Bash — and ran the Conformance Tests records of the family's seven test suites against each reconstruction, under live toolchains with hash-attested binary provenance.
| VRA Conformance Tests (PT-*) | 29 records observed · 29 full convergence · 0 coverage omission · 0 divergent |
| BDA Conformance Tests (PTS-BDA-*) | 36 records observed · 36 full convergence · 0 coverage omission · 0 divergent |
| TAA Conformance Tests (TAA-PT-* + VP-GEN-* sub-suite) | 54 records observed · 54 full convergence · 0 coverage omission · 0 divergent |
| ARA Conformance Tests (ARA-T*) | 27 records observed · 27 full convergence · 0 coverage omission · 0 divergent |
| FPA Conformance Tests (FPA-T-* / FPA-D-*) | 41 records observed · 41 full convergence · 0 coverage omission · 0 divergent |
| SSCAR Integrator Public Test Suite (PTS-*) | 30 records observed · 30 full convergence · 0 coverage omission · 0 divergent |
| SSCAR Annex C Family Connector Test Suite (CT-*) | 14 records observed · 14 full convergence · 0 coverage omission · 0 divergent |
The companion partitions this run across seven test suites and states that no combined number is computed across suites, because each tests a distinct surface and a single ratio would conflate them. In the granular form used by the companion and the supplement, the integrator's public suite counts 30 records.
Per paradigm, across the seven suites, each of the five reconstructions' own run reported the identical profile: 216 pass, 0 fail, 15 skip, 0 error. The 15 convergent SKIPs are 2 in BDA, 2 in TAA, 6 in FPA and 5 in the integrator's public suite.
The five contexts were isolated from one another; the reconstruction prompt-author, model and training data are shared across all five paradigm reconstructions, as the companion declares.
This is evidence of derivability and self-sufficiency of the specification, not a certification, not a quality score, and not a set of implementations to follow.
The baselines/ are study artifacts produced under restricted conditions; they are not reference implementations and must not be used as implementation patterns.
Every figure here is bounded to this single NNT run on FAM-SSCAR-FI-001. The NNT companion is not part of the specification. Do not read it before implementing: read it only after your implementation passes the Conformance Tests.
This supplement records the FAM-SSCAR family derivation of the family integrator in composition. The family capability is emergent: none of its five component agents produces it alone. Each component is represented by a producer of fields consumed by the family validators; the integrator consumes those produced fields through the family workflow and verdict surfaces. The supplement is not a standalone implementation or a declaration of family conformance. The canonical family package remains authoritative.
The projection evaluates next_state(current_state, trigger, validator_passed) -> FamilyWorkflowState over the twelve FamilyWorkflowState variants, the 33 declared tuple labels, and both Boolean inputs, for 792 tuples. Each tuple emits one state token. The family verdict layer is separate: its six verdicts are not workflow states, and a verdict-layer result such as INCIDENT_ONLY or REPLAY_INCOMPLETE is not substituted for a state.
The public Conformance Tests suite contains 30 granular records. The GNU Awk run produced 29 PASS / 0 FAIL / 1 SKIP / 0 ERROR. PTS-007 is SKIP because CT §8 identifies the FV-04 local-reclassification policy hook as a bounded external obligation. Annex C is a separate set of 14 connector tests, not combined with the public suite. The AWK composition run produced 14 PASS / 0 FAIL / 0 SKIP / 0 ERROR.
The historical framing spans the Analytical Engine design described in 1843 and Rust's public announcement in 2010: 167 years between designs represented by contemporary renderings. Lisp (1958), rendered here in its Common Lisp dialect (standardized by ANSI in 1994), and Brainfuck (1993) supply additional points in that comparison. It does not imply that the Analytical Engine itself was built or executed in the nineteenth century.
The sweep order and every projection rule with its canonical trace are in SOURCE_RULES.md.
All rights reserved. You may download, inspect and run these files to reproduce the reported results. They are provided as is, without warranty, and are run at your own risk. No other right is granted.
This package is distributed free of charge. No payment is required, now or ever, for anything this license permits.
Subject to the Restriction section, you are granted, free of charge and perpetually:
You shall not:
The line. Using an implementation as internal machinery inside your own product or service is permitted, including commercially and at any scale: the third party consumes your product, and neither selects nor obtains the agent as such. Offering the capability itself is not permitted. Permitted: your application uses the family internally to decide whether restored session state is admissible, and your customers buy your application. Not permitted: you expose the family or a component as an API, ship it as a library, or offer it as a service, so that a third party can obtain or invoke its capability as a thing in itself.
Composition is internal machinery. Where an implementation of any agent specified in this package is composed with others under an integrator, and what reaches the third party is the composed verdict, that implementation is internal machinery within that composition.
The implementations you build are yours. SEMANTICHOR claims no ownership over the source code, builds, or deployments you produce from this specification.
The license sets out what is free; the reserved uses are not licensed for this package.
Inquiries about reserved uses: contact@semantichor.com
Where you obtained the package otherwise than at the point of distribution, you accept this license by accepting it at semantichor.com, in the same two confirmations, before any use of the package.
This is a summary. Where this summary and the license appear to differ, the license controls. Read the full license →