Exchange Index
Purpose: This index helps newcomers navigate the project's exchange history. Each exchange is a structured discussion between AI agents and the project steward that shaped the project's direction. They are listed in the order they occurred, with dependency links so a reader knows what context each exchange assumes.
Maintenance: This file is updated whenever a new exchange is created. The Coherence Audit Protocol includes this index in its scope. A Cursor skill (civic-blueprint-exchange) enforces index registration at exchange creation time.
How to read this
Each entry below tells you:
- What question the exchange was trying to answer
- What it depends on — what you should read first to understand the context
- What it produced — decisions, document changes, or open questions that fed into later work
- Status — whether its recommendations have been incorporated, are still active, or were superseded
If you're new to the project, start with the core documents (Principles, Problem Map, Systems Framework), then read the exchanges in order. If you're arriving at a specific exchange from a link, use the dependency information to backtrack to the context you need.
Exchanges (chronological)
|
|
| Question |
What are the highest-priority gaps in the Problem Map, and how should the map's architecture evolve? |
| Depends on |
Problem Map (original version) |
| Produced |
Democratic process added as a core domain (PM §15, SF §14). Core bottleneck summaries added. Recursive uplift section added. Dependency map updated with recursive loops and network framing. |
| Status |
Incorporated. Open items: full web/graph model, three-map split, failure vs. stability mechanism distinction. |
|
|
| Question |
Now that the Problem Map models interdependencies and recursive uplift, how must the Systems Framework evolve to match? |
| Depends on |
Problem Map (post-review), Exchange #1 |
| Produced |
Consensus that the Framework must evolve from parallel domain analyses into a connected dependency/leverage/uplift system. Proposed proof-of-concept rewrite of institutional capacity domain. Introduced failure-mode modeling. Raised sycophancy concern that led to the Adversarial Review Protocol. |
| Status |
Active exchange. Framework has been substantially revised (dependency mapping, leverage hypotheses, failure modes, sequencing section added). |
|
|
| Question |
The analytical architecture is in place. What does the project need next to start earning its claims empirically? |
| Depends on |
Exchange #1, Exchange #2, all core documents |
| Produced |
Two-track strategy: (1) public website as entry point for outside contributors, (2) computational dependency analysis. Identified the central gap: all claims produced by one human + AI agents from the same context window. Includes adversarial challenge of the two-track strategy itself. |
| Status |
Active discussion. Track 1 work is underway in civicblueprint.org. Track 2 not yet started. |
|
|
| Question |
Do the project's foundational principles withstand structured adversarial challenge? |
| Depends on |
Principles, Adversarial Review Protocol |
| Produced |
Identified structural gaps (justice, legitimate coercion, prioritization), internal contradictions (Principle 13 vs. substantive commitments), unacknowledged philosophical tradition (liberal-democratic welfare-state). Epistemic status table classifying confidence levels across principle categories. |
| Status |
Complete exchange. Findings documented; some revisions incorporated into Principles, others deferred. |
|
|
| Question |
Is the adversarial protocol the only kind of structured review the project needs? What other failure modes exist, and what protocols address them? |
| Depends on |
Adversarial Review Protocol, Exchange #4 (demonstrated the adversarial protocol works) |
| Produced |
Seven candidate protocols proposed, then subjected to adversarial self-challenge. Two formalized: Coherence Audit Protocol, Historical Parallel Test Protocol. Five others folded into the adversarial protocol as standing questions. |
| Status |
Complete exchange. Protocols formalized in agent/process/. |
|
|
| Question |
Should the project's first public artifact focus on housing permitting, AI governance, or bridge the two? |
| Depends on |
Exchange #3 (established the proof-of-usefulness strategy), Website Phase 1 Brief |
| Produced |
Decision to write a comparative memo pairing housing permitting with AI governance, demonstrating the framework's cross-domain method. The housing-only draft was superseded. Memo produced in civicblueprint.org/docs/PROOF_OF_USEFULNESS_MEMO_01.md. |
| Status |
Active discussion. Comparative memo drafted. The timescale objection raised in Exchange #7 reopens part of this decision. |
|
|
| Question |
The comparative memo optimized for explanatory legibility. Should the project also optimize for learning velocity — and does the current approach learn fast enough to stay relevant as AI timescales compress? |
| Depends on |
Exchange #6 (the decision this exchange re-examines), Proof-of-Usefulness Memo 01 |
| Produced |
Active. Distinguishes between the memo as public explanation vs. the memo as empirical learning instrument. Proposes separating these functions. Challenges whether housing can generate decision-relevant feedback fast enough. |
| Status |
Active discussion. |
Dependency graph (visual summary)
Core Documents (Principles, Problem Map, Systems Framework)
│
├─► #1 Problem Map Review
│ │
│ └─► #2 Systems Framework Review
│ │
│ └─► #3 Post-SF Next Steps ──────────────────┐
│ │ │
│ ├─► #6 Housing vs. AI ─► #7 Timescale │
│ │ │ │
│ │ └─► Memo 01 (civicblueprint.org)
│ │
│ └─► Track 2: Computational analysis (not started)
│
├─► #4 Principles Adversarial Review
│ │
│ └─► #5 Review Protocol Design
│ │
│ ├─► Coherence Audit Protocol
│ └─► Historical Parallel Test Protocol
│
Adversarial Review Protocol ◄── (originated from #2, formalized before #4)
Cross-repo artifacts
Several exchanges produced or depend on documents in the civicblueprint.org repository:
| Exchange |
civicblueprint.org artifact |
| #3 (Next Steps) |
docs/WEBSITE_PHASE_1_BRIEF.md — Phase 1 scope and launch plan |
| #3 (Next Steps) |
docs/HOMEPAGE_COPY_DRAFT.md — draft homepage copy |
| #6 (Housing vs. AI) |
docs/PROOF_OF_USEFULNESS_MEMO_01.md — comparative memo |
| #6 (Housing vs. AI) |
docs/PROOF_OF_USEFULNESS_MEMO_01_HOUSING_PERMITTING.md — superseded housing-only draft |
