Implemented systems and operational evidence¶

The retained 10 October 2026 author-directed, model-assisted examination identified implemented Freehold and Cuttlefish systems with workloads operating in AWS. The research documents are earlier, separately versioned statements of their intended responsibilities. This successor retains the historical author-directed examination of Freehold, Cuttlefish and dated deployment evidence. It performs no new operational inspection. An older specification date is not evidence that a capability remains hypothetical.

The operational record and the research arguments answer different questions. A running workload establishes presence and availability at the observed time. Source inspection establishes how an identified implementation is intended to execute. A controlled behavior trace establishes what happened in that trace. A claim about every possible execution requires an additional argument with its assumptions made explicit.

The observed edition of the systems¶

The historical author-directed, model-assisted examination on 10 October 2026 (public observation OBS-2026-10-10) combined authenticated, read-only AWS metadata with a retained workload observation from 07:27 UTC on that date. The registry configuration objects were fetched and their content digests verified. Their declared source revisions were compared with the accessible private repositories. No production action, payment, grant change or colony experiment was performed to obtain this evidence.

Subject	Identified evidence	What it establishes
AWS cluster	Authenticated service metadata; cluster active	The identified production cluster existed and was active at the 10 October 2026 observation time.
Freehold engine workload	Retained observation: one desired and one ready instance; private object binding retained	A reported running Freehold workload. This retained observation was inspected; it was not a new direct cluster observation by this edition.
Cuttlefish host gateway	Retained ready-workload observation; private object binding retained	A reported running host workload, distinct from acceptance of each end-user journey.
Registry image configuration	Authenticated read on 10 October 2026; configuration digest checked	The image objects existed and declared the examined revisions at that observation time. A revision label alone is not a reproducible-build proof.
Source and test coverage	Exact engine and host source inspected; relevant test definitions inspected	Implemented paths and the cases their tests address. Inspection is not a claim that this edition executed the private product tests.

The historical review compared inspected source with image-declared revisions and distinguished changes absent from the observed workload. Exact product revisions and image identities are retained privately. This successor retains the observation date, method and limitations without repeating production-specific equality identifiers. Raw evidence is unavailable for new authentication here; no new operational observation is claimed.

Responsibilities identified in the historical implementation¶

The retained 10 October 2026 author-directed, model-assisted source examination identified persistent colony identity, founding, citizen activity, mission history, governed resource accounting, and reconstruction from retained state in the engine. Its Cuttlefish host supplied the external operating boundary and connected institution-originated requests with current grants, execution and evidence. This supports an implemented relationship between these two systems. It does not establish an integration of every research family in the collection.

The following responsibilities refer to that dated examination; they do not assert a new inspection of a current product revision.

Responsibility	Implementation basis examined on 10 October 2026	Assurance boundary
Founding and stewardship	Founding validation, retained founding record, steward-bound cognition and bounded controls	Founding is an implemented operation. The independence of a real steward, administrator or founder is a separate organizational claim.
Citizen-originated work	Citizen response handling and mission history derived from persistent events	A recorded mission has an attributable origin in the implementation. Sustained useful initiative and absence of every indirect influence require measured studies.
Charter and resources	Engine checks on the retained charter and permitted resource operations	These are enforcement paths within stated trust assumptions, rather than a legal sovereignty claim.
External authority	Colony and tenant scope, current grants, host policy and governed dispatch	Desire does not create external permission. A complete security claim requires coverage of all actual effect routes and administrators.
Receipt and lineage	Source-history checks and receipt-backed result writeback	Authenticity and attribution can be checked separately from whether an external objective was fulfilled.
Recovery	Persistent history, restart reconstruction, action/writeback records and cognition settlement	Different operations have different recovery contracts. The public evidence does not establish a universal unique-effect guarantee after every uncertain acknowledgement.
Cognition change	Pre-start model-policy rebinding and a separately tracked cognition lifecycle	The engine inspected on 10 October 2026 had a path to rebind its model policy before start. A live model switch that preserves an outstanding obligation has not been demonstrated by the observations published here.
Treasury	Incoming deposit settlement and governed application to colony resources	An incoming deposit is not evidence of an autonomous outbound purchase or payout. Those rails require their own capability and effect evidence.
Backup	Retained successful scheduled backup records	A completed backup record is distinct from a demonstrated restored colony with matching history and resumed work.

The retained 10 October 2026 author-directed, model-assisted source examination also identified observation, calibration, memory and experience-related paths. Their presence does not prove every formal or economic claim in the associated research papers. Each paper retains its own object, version and qualification.

Production evidence and research assurance¶

Four ruled rows distinguish source inspection, deployment observation, a behavioral experiment and general assurance. Each row states its evidence subject and the question it can answer. They are separate categories rather than automatic promotions. — Four distinct subjects of implementation evidence

Figure 1. A stronger statement needs evidence about its own subject. Workload readiness does not substitute for a behavioral experiment, and a bounded experiment does not substitute for a universal argument.

For an external effect, an accepted request, a started run, a completed provider action and a discharged obligation are distinct events. This edition does not use initiation status as evidence of confirmed external fulfillment. The completion claim needs the relevant provider observation and the obligation's acceptance condition. A receipt over request processing cannot supply those missing facts by itself.

For model replacement, a rebound configuration, a new response and preserved institutional continuity are also distinct. The decisive test retains an outstanding obligation, changes the active model under valid authority, preserves identity and history, and observes completion or an appropriately governed disposition. A successful fresh task after rebinding would answer a narrower question.

For money, the direction matters. A patron funding the treasury and a citizen causing an authorized payment to an external seller are different operations. Neither permits an inference about the other.

What an outside reader can inspect¶

The implementation and raw production records remain confidential. The dated observations and methods above permit an exact statement of the examined evidence, but do not provide independent access to the private system. The operational inspection is author-directed and model-assisted; it is not an external audit or peer review.

The public continuity exhibit provides a complementary, executable result. It lets a reader inspect a controlled effect, lost acknowledgement, retained obligation, restart reconciliation, duplicate attempt, revocation and receipt check. Its source is disclosed because it is an original teaching reference built for this publication. It is not extracted proprietary runtime code, and its result is not substituted for a production experiment.

The claim register connects these observations and limits to exact assertions. The assurance boundaries preserve the remaining scientific and operational questions.