# Rich Proposal Creation Plan - Mapped Rehearsal - 2026-07-09

Generated UTC: `2026-07-09T20:16:18Z`

## Scope

This is a clone/staging rehearsal for the supported subset of Cory-approved rich KB proposals after applying an explicit mapping overlay:

- `outputs/rich-proposal-creation-plan-20260709/reviewed-mapping-overlay-20260709.json`

The overlay is fail-closed: without it, the planner blocks unsupported edge types and external/context targets. The overlay maps only:

- `supersedes_component_of -> supersedes`
- `draws_from -> derives_from`
- `revises_or_refines -> supersedes`
- `rio:belief rank 1 / Capital allocation is civilizational infrastructure -> c0000000-0000-0000-0000-00000000000c`

It intentionally does not map telos/shared-root targets, Rio strategy context, governance gates, or concept-map storage into `public.claim_edges`.

## Planned Counts

| proposal | claims | sources | evidence | edges | blocked edge fragments | unresolved design decisions |
| --- | ---: | ---: | ---: | ---: | ---: | ---: |
| `14fa5ecc-ac7a-41c1-807d-a2e85b936617` | 4 | 9 | 11 | 7 | 6 | 2 |
| `ac036c9d-20a0-4ffe-881f-57d6b7bacf22` | 3 | 6 | 6 | 4 | 2 | 0 |

Total mapped supported subset: 7 claims, 15 sources, 17 evidence rows, 11 claim edges.

## Remaining Blockers

Still blocked because these are not safe `public.claim_edges` targets:

- `teleo telos`
- `teleo telos / fund-build paths toward better attractors`
- `rio:capital-deployment-layer`
- `rio:active strategy v1 / internet-finance capital product`
- `governance_gate:quality-gate`
- `governance_gate:evidence-bar`
- `concept_map:distributed_market_intelligence`

The live DB shows the telos target exists as `public.shared_root` row `13100000-0000-0000-0000-000000000001`, not a `public.claims` row. That requires a separate strategy/shared-root anchor lane, not a claim-edge mapping.

## Live Rollback Rehearsal

The mapped SQL ran against live `teleo` in rollback mode. Both transactions inserted rows in-transaction and rolled back cleanly. Production generated-row readback after rollback:

```text
generated_claim_rows  generated_source_rows  generated_edge_rows  generated_evidence_rows
0                     0                      0                    0
```

## Disposable Clone Commit Proof

Created disposable DB `teleo_mapped_rehearsal_20260709` from live `teleo`, converted only `rollback;` terminators to `commit;`, and applied the mapped SQL to the clone.

Clone readback after commit:

```text
generated_claim_rows  generated_source_rows  generated_edge_rows  generated_evidence_rows
7                     15                     11                   17
```

Production readback after clone commit:

```text
generated_claim_rows  generated_source_rows  generated_edge_rows  generated_evidence_rows
0                     0                      0                    0
```

Cleanup readback:

```text
disposable_db_exists
0
```

VPS service stayed stable after the rehearsal:

```text
MainPID=3252143
NRestarts=0
ExecMainStartTimestamp=Thu 2026-07-09 06:59:44 UTC
ActiveState=active
SubState=running
```

## Evidence Files

- Mapped plan JSON: `/Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/rich-proposal-creation-plan-20260709/rich-proposal-creation-plan-mapped.json`
- Mapped rollback SQL: `/Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/rich-proposal-creation-plan-20260709/rich-proposal-creation-plan-mapped.sql`
- Mapped clone commit SQL: `/Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/rich-proposal-creation-plan-20260709/rich-proposal-creation-plan-mapped-staging-commit.sql`
- Clone proof log: `/Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/rich-proposal-creation-plan-20260709/staging-db-mapped-commit-rehearsal-current.log`
- Generated-row count SQL: `/Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/rich-proposal-creation-plan-20260709/generated-row-counts-mapped.sql`

## Claim Ceiling

The mapped subset is clone-commit proven but not production-applied. Production apply still requires explicit authorization and a decision for the remaining non-claim targets, especially telos/shared-root and governance-gate storage.