IEF
Archive / Evidence Foundation • Media-Memory with Persistence
Closes the Lab media experiments with persistent anchors
- 01Cosmoscosmos
public field / quests / artifacts
- 02Room / Packetroom
bootstrap room, owned packet, intent capture
- 03SelfNodeself_node
capability router, admission, semantic modes
- 04IEFief
evidence, artifacts, quarantine, proof packet lanes
- 05RoundTableroundtable
inspection, skeptic review, proof packet attack
- 06Mainframe / Operatoroperator
operator shell, runtime posture, action readiness
- 07futureProjectionprojection
policy-gated public output, future public artifact
This rail shows how the organs relate. Runtime handoff still requires proof, RLS, and operator review.
Public signals become artifacts only after projection policy, evidence, and admission. The IEF lens labels each candidate with the lane it currently sits in.
- Purpose
- Recorded but not surfaced. Cheap, reversible.
- Admission condition
- Provenance check passed; nothing else asserted yet.
- Next route
- Deduplicate or decay if unattended.
- Purpose
- Falsifiable assertion extracted; evidence still pending.
- Admission condition
- Claim extraction stage emitted at least one testable statement.
- Next route
- Request evidence; route to skeptic for counter-falsification.
- Purpose
- Held without downstream effects until escalation.
- Admission condition
- Spoof/swarm signal or unresolved threat-class hit.
- Next route
- Route to operator, escalate, or decay on timeout.
- Purpose
- Independent artifact lands and is anchored to the claim.
- Admission condition
- At least one independent evidence artifact verified.
- Next route
- Route to RoundTable inspection before any projection.
- Purpose
- Authorised for the public surface as a published artifact.
- Admission condition
- RoundTable approved + projection policy signed off.
- Next route
- Publish as public artifact; archive with full provenance.
Each arrow is a checkpoint, not a transformation. A candidate that fails any check is sent to quarantine, decay, or discard — never silently to the next stage.
Proof packets are the unit of coordination evidence. Each packet sits in exactly one lane; promotion across lanes requires the lane’s exit condition.
Source of truth: apps/spine/lib/proof-packet-fixtures.ts. Every packet shown is synthetic. No proof packet here is runtime-backed or proven.
Recorded but not surfaced. Cheap, reversible.
- Entry
- Provenance check passed; nothing else asserted yet.
- Exit
- A claim is extracted from the observation that is single and falsifiable.
- Next route
- Deduplicate or decay if unattended.
Falsifiable assertion extracted; evidence still pending.
- Entry
- Claim extraction stage emitted at least one testable statement.
- Exit
- At least one independent evidence artifact is anchored to the claim.
- Next route
- Request evidence; route to a skeptic for counter-falsification.
Held without downstream effects until escalation.
- Entry
- Spoof / swarm signal or unresolved threat-class hit.
- Exit
- Operator review or evidence convergence resolves the hold.
- Next route
- Route to operator, escalate, or decay on timeout.
Independent artifact lands and is anchored to the claim.
- Entry
- At least one independent evidence artifact verified.
- Exit
- RoundTable inspection produces a verdict approving the next action.
- Next route
- Route to RoundTable inspection before any projection.
Authorised for the public surface as a published artifact.
- Entry
- RoundTable approved AND projection policy signed off.
- Exit
- Published artifact is anchored with full provenance; future updates follow the same gate.
- Next route
- Publish as public artifact; archive with full provenance.
“Claim is viral. Evidence is thin.”
- Evidence axes
- thread_url_snapshot · sender_continuity
- Telemetry keys
- proof_latency_seconds · evidence_velocity_per_minute · contradiction_density_ratio · attention_debt_units · blast_radius_units · reversibility_ratio
- Note
- Synthetic fixture only. Sits in the observed lane; no independent corroboration anchored yet.
“Document says ready. Cargo reality says wait.”
- Evidence axes
- customs_status · carrier_event · terminal_timestamp · gps · operator_note · invoice_state
- Telemetry keys
- proof_latency_seconds · evidence_velocity_per_minute · divergence_velocity_per_minute · attention_debt_units · contradiction_density_ratio · handoff_loss_count · execution_drift_units · blast_radius_units · reversibility_ratio
- Note
- Synthetic fixture only. Mirrors publicrepoconcept/examples/logistics-contradiction.proof-packet.json. No runtime backing.
“Engagement is high. Proof quality is low.”
- Evidence axes
- engagement_signal · evidence_quality_score · brigading_signal
- Telemetry keys
- evidence_velocity_per_minute · contradiction_density_ratio · attention_debt_units · blast_radius_units · reversibility_ratio
- Note
- Synthetic fixture only. Quarantined pending an offline-eval skeleton, per RFC do-not-publish-yet conditions.
Same chain that the existing lens documents. Repeated here so a packet card can be read alongside its full promotion path.
Fixtures show shape only. Runtime proof requires owned rows, RLS smoke, and operator review.
Container OS starts as evidence lanes, not carrier integration. The first contradiction is: “Document says ready. Cargo reality says wait.”
Source of truth: apps/spine/lib/container-os-fixtures.ts. No carrier / customs / GPS feed is connected. Every row is synthetic; no real cargo, partner, or document is referenced.
A shipping booking has been recorded against a vessel / route / window.
A pickup slot is committed; physical handoff is anticipated.
The unit has been physically collected from origin.
Gate-in event recorded at the receiving terminal.
Customs declaration has been submitted to the relevant authority.
Customs has authorised the unit to leave the controlled zone.
A status update emitted by the carrier (in transit, exception, ETA change).
Gate-out event recorded at the terminal as the unit leaves for delivery.
Physical delivery to consignee has occurred.
A slot for returning the empty unit has been committed.
The empty unit has been returned and the cycle is closed.
Free-time period at the terminal has started; cost accrues if it closes without release.
Free-time period has ended; demurrage charges apply unless released.
A damage claim has been opened against the unit / cargo.
A delivery route is committed for a single vehicle / single trip; the planned baseline against which deltas are measured.
A live position / speed / conditions sample has been captured along the route.
A single alternate route has been surfaced with a predicted delta in time / fuel / risk vs the planned baseline.
Operator has explicitly approved (or rejected) the reroute suggestion.
After completion, the actual time / fuel / risk delta vs the planned baseline is recorded.
- Source type
- customs broker / authority feed
- Proves
- Regulatory state of the unit; whether it is cleared to move.
- Risk if missing
- A "ready" claim cannot be reconciled with regulatory reality; demurrage and reroute risk grow.
- Source type
- carrier EDI / API feed
- Proves
- Latest scan, exception, or ETA update emitted by the carrier.
- Risk if missing
- No independent corroboration of in-transit state; document drift becomes invisible.
- Source type
- terminal operating system
- Proves
- Gate-in / gate-out time recorded at the terminal.
- Risk if missing
- Cannot establish whether the unit physically left or entered the controlled zone.
- Source type
- unit telematics
- Proves
- Physical location of the unit at a known timestamp.
- Risk if missing
- "Ready" claims cannot be ground-truthed against the physical world.
- Source type
- operator app / chat surface
- Proves
- Human-on-the-ground statement of fact, named and timestamped.
- Risk if missing
- Edge-case context is lost; only system feeds remain, which can be wrong together.
- Source type
- document management system
- Proves
- Current state of the commercial / shipping document.
- Risk if missing
- Commercial commitments cannot be reconciled with physical state.
- Source type
- terminal billing / contract reference
- Proves
- Whether the free-time clock is running and how much remains.
- Risk if missing
- Demurrage charges accrue silently; reroute decisions are made too late.
- Source type
- carrier / terminal slot system
- Proves
- Whether an empty-return slot is committed and confirmed.
- Risk if missing
- Cycle stays open; storage and per-diem costs accumulate after delivery.
- Source type
- incident management system
- Proves
- A damage claim has been opened with photos / witness records.
- Risk if missing
- Insurance recovery is undermined; liability is ambiguous.
- Source type
- route planner / dispatch system
- Proves
- The committed route, ETA, fuel budget, and risk score for a single trip.
- Risk if missing
- No baseline exists to compute predicted vs actual delta against.
- Source type
- vehicle GPS + sensor kit (synthetic)
- Proves
- Position, speed, and timestamp samples along the executed trip.
- Risk if missing
- Cannot ground-truth the actual route against the planned baseline.
- Source type
- condition feed (traffic / weather / hazard) — synthetic
- Proves
- External conditions affecting the route (congestion, weather, incident).
- Risk if missing
- Reroute suggestions cannot account for the field, only for the map.
- Source type
- minimal route simulator (synthetic)
- Proves
- Predicted change in time / fuel / risk if the reroute option is taken vs the planned baseline.
- Risk if missing
- Reroute suggestion has no comparable shape; operator cannot decide.
- Source type
- post-trip reconciliation
- Proves
- Actual change in time / fuel / risk after the trip completes; closes the loop with predicted_delta.
- Risk if missing
- The simulator never learns whether its prediction was right.
- Source type
- operator app / approval log
- Proves
- Operator explicitly approved (or rejected) the reroute before any action fired.
- Risk if missing
- Action fires without the approval gate; rollback note has no anchor.
“Document says ready. Cargo reality says wait.”
- Evidence trails
- customs_status · carrier_event · terminal_timestamp · gps_location · operator_note · invoice_document_state
- Note
- Seed contradiction. Synthetic only; no real cargo data anywhere in this fixture.
“Demurrage clock started. Booked release is missing.”
- Evidence trails
- demurrage_window · customs_status · carrier_event · terminal_timestamp · operator_note
- Note
- Synthetic only. Cost-of-error accrues by the minute once the window opens.
“Empty return is promised. Return slot is not confirmed.”
- Evidence trails
- empty_return_status · carrier_event · terminal_timestamp · operator_note
- Note
- Synthetic only. Cycle stays open until the empty-return event lands.
“Damage is reported. Evidence packet is incomplete.”
- Evidence trails
- damage_report · operator_note · carrier_event · invoice_document_state
- Note
- Synthetic only. Recovery / liability decisions wait on evidence convergence.
“Planned route says go. Live conditions suggest reroute.”
- Evidence trails
- planned_route · live_position · route_condition · predicted_delta · human_approval · actual_delta
- Note
- Synthetic only. Smallest delivery-route proof loop: one vehicle, one route, one reroute option, predicted vs actual time/fuel/risk delta, human approved before any action fires.
- Hat / scope
- evidence · selected_packet
- Expected output
- evidence pointer + confidence
- Suggested claim
- “Document says ready. Cargo reality says wait.”
- Approval
- none
- Hat / scope
- operator · selected_packet
- Expected output
- route / throttle / hold recommendation
- Suggested claim
- “Demurrage clock started. Booked release is missing.”
- Approval
- pending
- Hat / scope
- operator · selected_packet
- Expected output
- return slot confirmation path
- Suggested claim
- “Empty return is promised. Return slot is not confirmed.”
- Approval
- pending
- Hat / scope
- operator · selected_packet
- Expected output
- one reroute option + predicted vs actual delta (time / fuel / risk)
- Suggested claim
- “Planned route says go. Live conditions suggest reroute.”
- Approval
- pending
Same shape as the proof packet route, narrowed to the container-handoff axes (document / physical / contradiction).
Route proof loop: one route, one reroute option, predicted vs actual time / fuel / risk, human approved before action.
Synthetic fixtures only. Runtime use requires owned packets, proof packets, and operator review.