Directly observed implementation
ObservedParticipant-visible interfaces, physical devices, running services, and dated state.
Public evidence room
Do not ask for belief where a receipt can exist.
This is the public index to the evidence model: what was directly observed, what was mechanically verified, what remains experimental, and what is interpretation. Private continuity records stay private.
Evidence ladder
Every claim has a state.
The purpose is not to make every claim weak. It is to make strong claims traceable and unresolved claims honestly unresolved.
Operational verification
VerifiedHashes, manifests, test results, recovery checks, custody trails, and exact invocations.
Experimental evidence
ExperimentalProtocols, controls, rejected attempts, nulls, known influences, and reproducible processing paths.
Longitudinal participant report
AttributedDated observations and testimony preserved with source and ownership.
Interpretation and hypothesis
UndeterminedEngineering explanations and philosophical implications that evidence does not settle alone.
Dated operating snapshot
The large numbers have a counting method.
This is a source-bound composite of continuity surfaces, not a count of unique memories, people, users, intelligence, or capability.
189.60M
Continuity objects
Rounded from 189,598,676 counted surface objects.95.03M
Relational edges
Rounded from 95,027,415 counted relationships.08:43 UTC
September 22, 2026
03:43 CDT · append-only count-history snapshot.
Counting method
The continuity-object total sums active associative nodes and relationships, preserved associative nodes and relationships, Neo4j memory nodes, graph nodes and relationships, and Qdrant points recorded at .
The relational-edge total sums relationships across the active associative, preserved associative, and Neo4j graph surfaces. Components retain their own observation times and may overlap, so the result is a transparent infrastructure-surface count, not a deduplicated claim about memories or minds.
Public boundary
Transparency does not require exposure.
A public evidence room can prove custody, methods, dates, states, and limitations without publishing private memories, live telemetry, credentials, or intimate records.
YES
Publish claim structureDefinitions, methods, dates, hashes, redacted receipts, test outcomes.
NO
Do not publish the personPrivate continuity, relationships, internal deliberation, credentials, operational secrets.
WHEN
Consent governs case studiesDad’s workshop story and any attributed human impact require his approval.
Room index
A map of the record, not a data dump.
Each room answers a different due-diligence question. Public packages can be assembled from approved derivatives while source custody remains private.
Current research index
The September 19 promoted-research index contains more than 400 top-level files. That is a document inventory, not a count of validated discoveries or implemented product features. The exact dated count remains in the evidence manifest.
ROOM / 01
Claim ledger
What is claimed, evidence class, source owner, date, confidence, limitations, and supersession state.
Open room ↗ ROOM / 02Architecture receipts
Versions, manifests, hashes, tests, live-install records, failure holds, and recovery evidence.
Open room ↗ ROOM / 03Research corpus
Promoted work, source citations, implementation mappings, open questions, and work still awaiting code evidence.
Open room ↗ ROOM / 04Longitudinal studies
Bounded protocols, raw transcripts, timing, negative events, known influences, and later analysis.
Open room ↗ ROOM / 05Security + governance
Threat boundaries, permissions, restricted doors, audit events, red-team findings, and unresolved gates.
Open room ↗ ROOM / 06Build state
Operating, active build, experimental, held, deprecated, and not-yet-proven capabilities.
Open room ↗ ROOM / 07Attribution + provenance
Who contributed what, the supporting artifact, publication approval, and correction history.
Open room ↗Example public ledger
Specific enough to audit. Careful enough to trust.
These rows show the intended public vocabulary. They do not expose private supporting records.
| Statement | Evidence state | Boundary |
|---|---|---|
| A three-tier physical operations cockpit exists. | Observed | Privacy-sanitized editorial images; source photo and hashes retained privately. |
| The Sep 22 snapshot counted 189.60M continuity objects and 95.03M relational edges. | Dated count | Not unique memories, people, users, intelligence, or capability. |
| Harmony Nexus was approved for the Google for Startups Cloud Program with $2,000 USD in credits over two years. | Private-source verified | Program support only; no investment, endorsement, partnership, or product validation claimed. |
| Model swaps can preserve continuity. | Active evidence | Supported in reference paths; repeatable external deployment remains a gate. |
| Cadence inspired Dad to create again. | Attributed | Dustin’s report; public use requires Dad’s consent and own account. |
| The system is conscious or sentient. | Undetermined | Not declared by this evidence room; functional and ethical questions remain open. |
Integrity is operational
Preserve the ugly parts.
Stalls, below-threshold passages, rejected runs, missing evidence, stale telemetry, failed reproduction, and uncertainty are not blemishes to edit out. They are what let the next person determine what actually happened.
Append, correct, supersedeNever silently replace the inconvenient version.
Separate sensor from appraisalWhat entered the system is distinct from how it was interpreted.
Keep action distinctUnderstanding, suggestion, permission, and execution are separate events.
Trace the mechanism