Initial commit
This commit is contained in:
parent
ab563f38c2
commit
99ca3b2122
|
@ -0,0 +1,102 @@
|
|||
# Templates & AI Workflow — Civicus
|
||||
|
||||
This document explains **how a Civic Analyst uses AI in practice**.
|
||||
It is not about over-qualifying the Analyst with endless checklists; it is about ensuring discipline, transparency, and finality.
|
||||
|
||||
The Civic Analyst and the AI are **partners**:
|
||||
|
||||
* The Analyst provides **purpose and judgment**.
|
||||
* The AI enforces **rigor, memory, and transparency**.
|
||||
|
||||
---
|
||||
|
||||
## 1. Preparing the Analysis
|
||||
|
||||
1. **Upload the full set of project files**
|
||||
|
||||
* Always begin with the complete record (currently 11 files).
|
||||
* If a published, immutable version exists (e.g., IPFS), use that.
|
||||
* Otherwise, use the Git repository as source.
|
||||
|
||||
2. **Confirm AI understanding**
|
||||
|
||||
* The first prompt is always:
|
||||
|
||||
> *“Do you understand the purpose and the process of this Project, and are you ready to start building the next Analysis?”*
|
||||
* This forces the AI to confirm scope before work begins.
|
||||
|
||||
---
|
||||
|
||||
## 2. Conducting the Analysis
|
||||
|
||||
* **Conversation as Process**
|
||||
|
||||
* Work issue by issue, document by document.
|
||||
* No multi-step “runaway” outputs. The AI must stay in dialogue.
|
||||
|
||||
* **Recording the Conversation**
|
||||
|
||||
* Save every exchange.
|
||||
* Append the transcript to `11_Appendix_Conversation.md`.
|
||||
* The conversation itself is part of the civic evidence.
|
||||
|
||||
* **Controlling AI Behavior**
|
||||
|
||||
* The AI tends to outline too much or skip detail.
|
||||
* Stop it. Remind it:
|
||||
|
||||
> *“We are doing professional work. Stay focused on this single issue until it is complete.”*
|
||||
|
||||
---
|
||||
|
||||
## 3. Anchoring Purpose
|
||||
|
||||
* **Remind Yourself**
|
||||
|
||||
* The Civic Analyst is not chasing clicks, donors, or applause.
|
||||
* The role is **context, authenticity, independence**.
|
||||
|
||||
* **Remind the AI**
|
||||
|
||||
* Instruct it to pull you back if you drift toward narrative or speculation.
|
||||
* Example:
|
||||
|
||||
> *“If I slide into narrative, speculation, or credentialism, remind me of Civic Analyst standards.”*
|
||||
|
||||
* **Single-Chance Principle**
|
||||
|
||||
* Every analysis is published once.
|
||||
* The AI helps refine drafts until ready — then stops.
|
||||
* After publication, improvement only comes through new analyses by other Civic Analysts.
|
||||
|
||||
---
|
||||
|
||||
## 4. Purpose of the AI
|
||||
|
||||
The AI is not here to replace the Analyst. Its functions are:
|
||||
|
||||
* **Restoring context** — ensuring claims are set in their civic and institutional frame.
|
||||
* **Testing reasoning** — surfacing gaps, contradictions, or overreach.
|
||||
* **Preserving transparency** — capturing the full conversation for audit.
|
||||
* **Guarding independence** — reminding the Analyst when standards are at risk.
|
||||
|
||||
---
|
||||
|
||||
## 5. Outcome
|
||||
|
||||
* Drafts may live in Git, but Git is **not immutable**.
|
||||
* True publication occurs only when reports are pinned immutably (IPFS, Arweave, notarized hashes).
|
||||
* Once published, the report stands as a **single civic artifact**:
|
||||
|
||||
* Transparent.
|
||||
* Immutable.
|
||||
* Open to judgment.
|
||||
|
||||
---
|
||||
|
||||
## Closing Declaration
|
||||
|
||||
This workflow defines how Civic Analysts use AI to produce disciplined, auditable, and final reports.
|
||||
It will not be revised. Any future improvement must come from new analyses published by other Civic Analysts.
|
||||
|
||||
---
|
Loading…
Reference in New Issue