ROUNDTABLE
Media-Memory Coordination • Gentlemen Agreements
- 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.
Media-Memory Coordination Surface
RoundTable does not pick winners. It attacks assumptions before a scenario reaches operator pilot.
Sources of truth: apps/spine/lib/pilot-scenario-fixtures.ts and apps/spine/lib/scenario-loop-fixtures.ts. Private and operator-only rows are filtered out of this lens. No scenario shown here is approved, proven, or scheduled for any pilot.
“Document says ready. Cargo reality says wait.”
- Evidence trails
- customs_status · carrier_event · terminal_timestamp · gps · operator_note · invoice_state
- Telemetry
- proof_latency · evidence_velocity · contradiction_density · handoff_loss
- Next artifact
- fixture-ready proof packet (already drafted in publicrepoconcept/examples).
- What would falsify this?
- What evidence is missing?
- What is the blast radius if wrong?
- What should stay private?
“Claim is viral. Evidence is thin.”
- Evidence trails
- thread_url_snapshot · independent_corroboration · time_window_recurrence · sender_continuity
- Telemetry
- evidence_velocity · contradiction_density · attention_debt · public_signal_admission_ratio
- Next artifact
- short red-team prompt + admission lane fixture.
- What would falsify this?
- What evidence is missing?
- What is the blast radius if wrong?
- What should stay private?
“Engagement is high. Proof quality is low.”
- Evidence trails
- evidence_quality_score · brigading_signal · spoof_pressure · projection_consistency
- Telemetry
- evidence_velocity · contradiction_density · attention_debt · blast_radius
- Next artifact
- cite the existing RFC draft + add an offline eval skeleton.
- What would falsify this?
- What evidence is missing?
- What is the blast radius if wrong?
- What should stay private?
“Mission survives. Problem does not close.”
- Evidence trails
- stated_objective · budget_trail · closed_case_count · beneficiary_outcome
- Telemetry
- proof_latency · execution_drift · attention_debt · reversibility
- Next artifact
- one-page memo framing drift as measurable, not moral.
- What would falsify this?
- What evidence is missing?
- What is the blast radius if wrong?
- What should stay private?
“Artifact wants public surface. Privacy / risk boundary may block it.”
- Evidence trails
- projection_policy_decision · roundtable_verdict_log · redaction_diff · public_artifact_hash
- Telemetry
- blast_radius · reversibility · projection_consistency
- Next artifact
- projection-policy fixture skeleton.
- What would falsify this?
- What evidence is missing?
- What is the blast radius if wrong?
- What should stay private?
“Founder intent and operator next action diverge.”
- Evidence trails
- founder_packet_intent · operator_decision_log · recent_actions · roundtable_verdict_history
- Telemetry
- execution_drift · attention_debt · proof_latency
- Next artifact
- one-line drift-detector heuristic for the runbook.
- What would falsify this?
- What evidence is missing?
- What is the blast radius if wrong?
- What should stay private?
“Agent output looks useful. Action safety is unproven.”
- Evidence trails
- agent_invocation_envelope · capability_request · rollback_note · human_approval_artifact
- Telemetry
- reversibility · blast_radius · attention_debt
- Next artifact
- agent envelope checklist consumable in @invoke contract.
- What would falsify this?
- What evidence is missing?
- What is the blast radius if wrong?
- What should stay private?
- 01Signal observed — exit: The signal is named and the contradiction is one sentence.
- 02Scenario card — exit: Every required template field (oneCaseTemplateFields) is filled in.
- 03Fixture ready — exit: The card is encoded into a static fixture row in the repo.
- 04Proof packet ready — exit: At least one independent evidence artifact is anchored to the claim.
- 05RoundTable ready — exit: A multi-actor RoundTable verdict has been recorded.
- 06Operator pilot ready — exit: A bounded operator pilot is launched with a written rollback note.
- 07Public projection ready — exit: Projection policy explicitly authorises a public artifact.
- many_until_roundtable— Many cards run in parallel until RoundTable
- one_operator_pilot_at_a_time— One operator pilot at a time
- public_projection_requires_policy— Public projection requires projection policy
- private_scenarios_stay_private— Private scenarios stay private
- proof_promotes_not_enthusiasm— Proof promotes; enthusiasm does not
A scenario reaches operator pilot only after proof packet readiness and RoundTable review.
RoundTable inspects proof packets before operator action. A packet can be attacked without being approved.
Source of truth: apps/spine/lib/proof-packet-fixtures.ts. Every packet shown is synthetic. No proof packet here is runtime-backed or approved.
“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.
“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.
“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.
- What would falsify this claim? — Forces the claim to be falsifiable and not a slogan.
- What evidence is missing? — Names the next concrete deliverable on the promotion path.
- What should stay private? — Identifies projection-policy boundaries before any publish action fires.
- What is the blast radius if wrong? — Bounds the cost of admitting the claim without sufficient evidence.
- What would make this eligible for projection? — Surfaces the explicit gate from evidenced to projected.
- What operator action is safe before certainty? — Names the lowest-risk reversible action the operator may take while evidence is still being gathered.
The same chain documented on /ief and /self-node. RoundTable sits between artifact and operator.
Inspection produces questions first. Verdicts come later.