Read these cards when a chamber term is unfamiliar. They explain the relationship between evidence, interpretation, runtime architecture, the visible Audralia world, and its diagnostic reflection. Opening a card changes presentation only; it does not run a report or cycle.
Audralia Dreamscape
Engine Diagnostic Chamber
Diagnostic controls awaiting boot
REPORT AVAILABLE
SAFE_REPORT
Audralia Dreamscape
Follow DREAM from evidence to world reflection.
DREAM is the path through the chamber. DROP gathers evidence. READ interprets it. The 3D Engine System powers the architecture. Audralia expresses the visible world. Mirrorland reflects that world for diagnosis.
D Evidence gathering DROP Gather bounded evidence.
Explicit participant or cycle action only.
Readable record from current evidence.
Target, runtime, registry, aliases, receipts, and surface evidence.
Diagnostic components, methods, status, and direction.
R Evidence interpretation READ Interpret the evidence.
What current evidence establishes.
Receipts, globals, paths, contracts, and observations.
Missing, held, unknown, inaccessible, or erroneous evidence.
The next file, owner, authority, or action to inspect.
E Interactive infrastructure 3D Engine System Power the system.
Defines permitted behavior and boundaries.
Coordinates runtime execution and receipts.
Records authorities, engines, subjects, and slots.
Observe evidence and recommend next directions without production mutation.
A Visible world expression Audralia Express the world.
Terrain, water, atmosphere, motion, controls, and visible subject behavior.
The visible world remains separate from diagnostic mutation.
M Bounded reflection Mirrorland Reflect the world for diagnosis.
Contracts, authorities, runtime evidence, receipts, holds, and directions.
Mirrorland does not create a second production runtime.
Continue from DREAM into the diagnostic track.
Choose the report context, then open deeper controls only when needed.
Open Work workspace
Focused diagnostic track
Diagnostic Workspace
Choose one workspace at a time. Tabs change what is shown; only a labeled operation creates a report, runs a direct check, or starts Nine-Cycle.
Workspace Work
Category Observatory / Receiver
Audit Observatory Index
Participant None selected
Choose Category and Audit to define the report context. Use Participant Context only for a direct check. Selection alone is read-only; Create Report, Run Direct Check, and Run Nine-Cycle are the only operations here that request new diagnostic state.
Selection does not execute. Direct checks require one selected participant. Nine-Cycle remains a separate explicit action.
Diagnostic family
Participant Constellation
Select one participant to establish explicit direct-execution context.
Required 10
Optional 1
Available 0
Held 0
North ConductorRequired · Cycle authority
UNKNOWNF1 · North IntakeRequired station
UNKNOWNF3 · East SourceRequired station
UNKNOWNF5 · East ConstructionRequired station
UNKNOWNF8 · Canvas Surface TruthRequired station
UNKNOWNF13 · West RuntimeRequired station
UNKNOWNF21 · West InterpretationRequired station
UNKNOWNF34 · South HandoffRequired station
UNKNOWNF55 · South RestitutionRequired station
UNKNOWNSouth Surface PointerOptional auxiliary · F55 parent
UNKNOWNF89 · Rail SynthesisRequired station
UNKNOWNSelect a participant
Path, required status, contract, version, cycle position, aliases, and callable methods will appear here.
Explicit and secondary commands More Operations Direct · Cycle · Packet · Raw · Archive · Reset
Direct execution requires one participant selected from the Participant Context tab.
Current diagnostic evidence
System Status
Target, runtime, station, mount, frame, and DROP lane state.
Status chips summarize what the chamber has observed, not what presentation implies. Unknown means no bounded evidence has been established; Held means an attempted path could not proceed. Return to Work to request a report or explicit execution.
Target · Unknown
Runtime · Unknown
Renderer · Unknown
Surface · Unknown
North · Unknown
East · Unknown
West · Unknown
South · Unknown
Cycle · Not Run
Registry · Unknown
Mount · Unknown
Canvas · Unknown
Frame · Unknown
Direct Execution
IDLE- Available
- 0
- Held
- 0
No direct command has been executed.
Report
AVAILABLE- Available
- 1
- Held
- 0
Create Report is available immediately.
Observation
OBSERVING- Available
- 0
- Held
- 0
Lightweight observation begins after diagnostic-engine boot.
Participant
LOADING- Available
- 0
- Held
- 0
Inspecting shell-preloaded diagnostic participants.
Observatory / Receiver
Observatory Index
Summarize the diagnostic shell, bridge, inspection lane, engine, controls, participants, observations, registry, and current state.
READ separates Result, Evidence, Absence, and Direction so a finding is not confused with missing proof or a suggested next step. The report establishes only the selected context and current evidence. READ, Packet, Raw, and Evidence tabs change presentation only.
StatusAVAILABLE
ReportNo report created
Created—
Choose a category and audit, then create a report. Report availability does not certify runtime or family readiness.
Result
Chamber availableCreate a report to evaluate the selected diagnostic context.
Evidence
Shell declaredDGB family, diagnostic family, report chamber, controls, target frame, and evidence containers are declared.
Absence
No report yetNo current report, direct check, or nine-cycle result exists.
Direction
Create the first reportUse the control pad to select the context and create its diagnostic record.
No report packet has been created.
No raw report has been created.
No evidence report yet
Create a report to collect current evidence.
Lower evidence field
Cycle, registry, receipts, archive, and boundaries
Choose Cycle, Registry, Receipts, Archive, or Boundary to inspect one evidence family. Chamber tabs change presentation only. Nine-Cycle runs only from its labeled Work operation; Registry and Boundary do not certify runtime readiness.
Explicit execution audit
Nine-Cycle Chamber
Current evidence may be reported before a cycle exists.
Nine stations and auxiliary context register only during execution.
Bounded target-runtime preflight belongs to Run Nine-Cycle.
No conductor cycle exists during this session.
Station navigatorF1 → F89 station map Nine station questions and current receipt state
- 1North IntakeF1
What are we diagnosing?
- 2East SourceF3
What was declared?
- 3East ConstructionF5
Is the construction admissible?
- 4Canvas Surface TruthF8
Is there a valid 3D presentation host?
- 5West RuntimeF13
What runtime evidence exists?
- 6West InterpretationF21
Does source match runtime?
- 7South HandoffF34
Can the packet return cleanly?
- 8South RestitutionF55
What owner or continuation is recommended?
- 9Rail SynthesisF89
What is the final diagnostic reading?
Technical recordCycle Ledger Bounded raw rendering state
No cycle ledger has been produced.
Returned evidenceStation Receipts Receipts created only by explicit Nine-Cycle execution
No cycle receipts
Run Nine-Cycle explicitly to create station receipts.
Engine and authority records
Registry Chamber
Registry not observed yet
The DGB engine registry will be inspected after diagnostic boot.
Selected Engine
No selected-engine record has been observed.
Runtime Evidence
No engine-runtime evidence has been observed.
Durable diagnostic evidence
Receipt Chamber
No receipts collected
Reports, inspection, participants, observations, direct checks, cycles, and errors may contribute receipts.
Select a receipt
The normalized receipt detail will appear here.
Session evidence
Archive Chamber
No archived reports
Create a report and add it to the archive.
No archived errors
Engine and control errors will be recorded here.
Participant Snapshot
No participant snapshot has been archived.
Observation Snapshot
No observation snapshot has been archived.
Technical recordDeep ArchiveBounded raw session evidence
No deep archive has been created.
Permanent no-touch declarations