docs/SOURCE_ORIENTATION_REPORT.md

Source Orientation Report — v0.2.0

Scope

The prototype was rebuilt after reviewing the mounted creator-distribution specification, DPIO blind/repair/red-team lineage, Primordial Calculus model, Digital Mycelium current and Atlas packages, Loop-Gated OAM descendant, Substrate runtime organs, route runner, collaborative discovery layer, education/accessibility lineage, and the bounded creator-distribution causal-arc materials.

The source corpus mounted for orientation was approximately 2.7 GB. The public prototype does not simply copy that entire corpus. It separates:

• embedded architecture lineage needed to understand and reproduce the prototype;
• extracted governing contracts used by the runtime;
• hash-indexed private/heavy evidence that must not be silently republished.

Source-derived governing structure

Creator trace capsule

The atomic object is the creator_trace_capsule, not an accusation, platform verdict, political label, or proposed mechanism. The capsule preserves creator topology, baseline, events, evidence assets, metric receipts, claims, uncertainty, consent, correction ancestry, and source-return requests.

Four-lane causal surface

Every procedural read separates:

1. OBSERVED_FACTS
2. CREATOR_REPORTED_CONTEXT
3. SUPPORTED_INFERENCES
4. UNRESOLVED_CAUSES

This prevents testimony from being discarded while preventing testimony from silently becoming mechanism proof.

DPIO execution order

The frozen order is:

SOURCE_REGISTERED
→ EVENTS_REGISTERED
→ CHRONOLOGY_MAPPED
→ CAUSAL_FAMILIES_COLLAPSED
→ PREDICTIONS_FROZEN
→ HYPOTHESES_FROZEN
→ PRESSURE_TESTED

The order is material. Hypotheses may not be selected first and backfilled from the complete record.

Primordial Calculus causal law

The source model contributes temporal ratchets, causal-family deduplication, minimum cuts, institutional state variables, and the laws:

Authority(State_t) ≤ Support(Lineage_t)
Certainty(Conclusion) ≤ Strength(WeakestLoadBearingEdge)
ΔState_material ≠ 0 ⇒ Explanation or LatentEdge

A minimum-cut intervention can establish dependency without independently establishing motive.

Digital Mycelium holographic gate

Individual traces must remain source-bound, uncertainty-preserving, rehydratable, and separately reviewed before stacking. Fusion cannot hide STRAINED or MUST_STOP states. Archive presence is not equivalent to live continuity.

Loop-Gated OAM boundary

Constraint is not authorization. A pressure signal does not grant action authority. Repair does not settle the underlying claim. Release guards, receipts, and human review remain separate gates.

Substrate runtime organ chain

The reviewed runtime lineage maps to:

INGESTION
→ HYDRATION
→ RELATION MAP
→ INVOKE / ROUTE
→ SYNTHESIS
→ COUNTER-OAM
→ REHYDRATION
→ HUMAN VALIDATION
→ BUILD QUEUE
→ COCKPIT / CONTINUITY AUDIT

v0.2.0 implements this chain in a bounded creator-evidence form rather than carrying organ names as documentation only.

Creator-distribution evidence boundary

The source materials support preservation of recurring externally observable phenotypes such as documented distribution contraction, notification discrepancies, non-restoration after a reported state change, and weak human reciprocity. They do not independently establish the precise internal classifier, manual targeting, training use, executive authorization, or intent.

The X evidence corpus and videos remain hash-indexed rather than included in the public application package. Curated causal-arc contracts are included to preserve architecture without publishing the private evidence body.

Resulting implementation decision

The first source-complete prototype is:

CREATOR INTAKE ORGAN
+ SOURCE-ACCOUNT METRIC LEDGER
+ DPIO PROCEDURAL READER
+ MINIMUM-CUT WORKSHEET
+ CONTINUITY AUDITOR
+ CONSENT-GATED HOLOGRAPHIC COMPARATOR
+ LINEAGE REGISTRY

It is not a class-action verdict engine, motive detector, automated accusation system, or public evidence database.