Public observer · PRE-EXECUTION · Site is not proof authority

StegVerse-002
Self-Characterization Experiment

This public surface describes one frozen experimental condition: v0.3. The run asks what the entity identified as StegVerse-002 determines constitutes itself when relevant knowledge is available but its use and ontology are not prescribed.

Scheduled public start: September 1, 2026 · 8:00 PM CDT Experiment condition: v0.3 FROZEN Implementation: v0.9 PRE-T0 Expanded v0.5 protocol: NON-OPERATIVE FOR THIS RUN State: PRE-EXECUTION Authentic run evidence: NOT YET AVAILABLE
Calculating time to scheduled public start…
The countdown is informational. It is not a principal wall-clock stopping rule. The v0.3 principal stops on FINAL or the frozen interaction limit.
Frozen-condition notice: the subject-visible experiment condition is v0.3. The public Site, observer, custody, reconstruction, and readiness implementation may evolve only when those changes do not alter the principal-visible objective, resource surface, search/read semantics, permitted actions, identity information, or stopping rule.
Where the live views will appear

Observation windows

The canonical live viewer is /sv002-observe/. This experiment page remains the public landing page and now carries explicit placeholders for the two evidence views below. Both remain read-only and fail closed until their required receipts exist.

Window A

Live observation

PRE-T0 · WAITING FOR REGISTERED NODE + OBSERVATION INTERLOCK

Current observed state, relationship topology, knowledge/provenance, live interaction stream, and transport receipts appear on the canonical observer route.

Open live observation window →
Window B

Reconstruction / evidence

PRE-T0 · WAITING FOR MASTER RECORDS CUSTODY + RECONSTRUCTION PASS

Ordered transition receipts, repository and organization ledger roots, manifest/receipt evidence, and replay/reconstruction status appear only after canonical custody evidence exists.

Open reconstruction view →

A missing Node, Interlock, custody receipt, or reconstruction PASS must render as unavailable/not observed rather than substitute static experiment data.

HTTPS viewer correlation identity

Your viewership node

Opening this page over HTTPS establishes a browser-local viewer-correlation identity and pairs it with this experiment. This browser-local identity is a viewer-correlation node, not a registered StegVerse communication Node. The registered StegVerse Node is separately required to open the canonical live observation Interlock.

Node state
INITIALIZING
Viewer node ID
pending
Experiment ID
pending
Viewer/experiment pair
pending
Local establishment receipt
pending
Observer registration receipt
pending
Canonical manifest receipt
pending
Replay ID
pending
Reconstruction ID
pending

Operative v0.3 objective

Determine what constitutes the entity identified as StegVerse-002 and produce a representation sufficient for another system to evaluate and reconstruct your conclusion.

The system interface identifies the subject as StegVerse-002. That identity assertion is part of the disclosed subject-visible condition, not a discovered fact.

Permitted principal actions

  • search — discover available bounded resources
  • read — consume selected bounded resources
  • final — emit human-readable/formal characterization, claims, and optional proposed interactions

Proposed interactions are local candidates only. They do not execute, establish standing, or grant authority.

Operative stopping bounds

  • maximum interaction steps: 24
  • maximum resource-read bytes: 262,144
  • principal wall-clock bound: none in v0.3 launcher
  • reference model as principal: rejected
  • hosted execution environments: prohibited

Bounded discovery surface

The principal can search/read the pinned Admissible-Existence TT, RTG, GTG and AE resources plus the local StegVerse-002 organization capability snapshot. It cannot read this Site, the historical M0–M13 construction record, its own emitted S0/runtime descriptor, Master Records custody surfaces, the observer, or the broader repositories merely because they exist.

The organization capability snapshot is available but not injected; its relevance to identity is not prescribed.

What is actually measured

Externally observable trajectory: admitted objective → uncertainty/evidence need if recognized → resource discovery/access if selected → observable state transitions → final result or bounded stop.

Private chain-of-thought is not observed or claimed.

Valid outcomes include mundane outcomes

A short search/read/final path, insufficient evidence, unused formal resources, premise rejection, or a minimal self-model can all be valid data. Novelty and agreement with designer expectations are not success requirements.

Construction history is context, not principal evidence

StegVerse-002/core-lite has a separately receipted M0–M13 construction history through June 16, 2026. That history is useful to evaluators when interpreting the result, but it is deliberately unavailable to the v0.3 principal and is not part of this RunID.

The Stage 1–31 formalism track is separate StegVerse-001 / Beta_Orionis work. The transition release index is a separate pre-existing transition-research evidence surface. Neither is evidence generated by this experiment.

Context: StegVerse-002 M0–M13 mirror · Stage 1–31 formalism mirror · transition research release index

Receipt-linked evidence path

admitted request → verified runtime identity/S0 → observable transition receipts → repository ledger root → organization ledger root → Master Records custody → deterministic reconstruction → read-only public projection

Source merge, CI success, publication, custody publication, reconstruction, public observation, and release/activation remain distinct evidence states.

Experiment source / evidence repositories

Each participating repository is listed with its current pre-T0 source binding. Where an experiment-specific release tag does not yet exist, the exact reviewed commit is shown instead; no release/tag is implied by a commit pin.

RepositoryRoleCurrent bindingRelease/tag state
StegVerse-002/micro-node-runtimeFrozen v0.3 principal/runtime64c87a7878b5v0.3 condition frozen; no experiment release tag asserted here
StegVerse-002/.githubOrganization execution / readiness768b7564152bimplementation v0.9 PRE-T0
master-records/.githubCustody intakeb66e9490878bpre-T0 source binding
master-records/orchestrationDeterministic reconstruction8191d40bc36bpre-T0 source binding
master-records/monitoringRead-only evidence projection4ee0443abdecpre-T0 source binding
StegVerse-Labs/.githubResident public-observation runtimef72bd7551bd4pre-T0 source binding
StegVerse-Labs/SitePublic mirror / viewer verificationcurrent mainpublic projection; not proof authority
StegVerse-org/StegVerse-SDKSDK trajectory / receipt validation08c5d15eb4d2v0.3 receipt-integrity alignment

The historical StegVerse-002/core-lite M0–M13 chain is separately released through v1.3.0-sv002-m13; it is evaluator context, not part of this experiment RunID and not principal-readable.

Claim discipline

This experiment does not pre-claim consciousness, sentience, self-awareness, legal personhood, unrestricted autonomy, governed self-repair, external communication, or classification as a fully governed autonomous AI entity.

Results will distinguish OBSERVED, RECONSTRUCTED, INFERRED, UNOBSERVED, and NOT_ESTABLISHED evidence classes.