Repository navigation
docs: the poll pipeline walked end-to-end + tracking template - #54
Merged
Merged
Conversation
Add docs/PIPELINE.md: the poll lifecycle followed literally from composing a question through the owner decoding answers, naming the concrete workflow/file behind each step and drawing the gaps as dotted lines that cite OPEN-QUESTIONS (authoring §J, registration validation §A/§B, QR provenance §L, exposure window and per-poll registry §F, batch cadence §K, aggregation §C). It is connective tissue: it composes existing pieces, adds no behavior. Add a poll-lifecycle issue template (+ config.yml) whose checklist mirrors the pipeline one checkbox per step, so a poll's progress lives in the open. Link the new doc from README.md and VISION.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FKUK1XzKwHCYDbwqHiuuNF
This was referenced Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the missing connective tissue for the poll lifecycle: a single document that follows a poll literally, step by step, naming the exact workflow/script/file behind each step and drawing the still-open seams as dotted lines.
docs/PIPELINE.md— the 12-step lifecycle (compose → copy the data-pile template → configure the question → register the pile with the Tell → mint the QR → answer-intake → Tell seals encrypted chunks → pile pulls/verifies → retention → owner decodes → aggregate). Each step is marked ─ wired or ┄ gap; every dotted line citesOPEN-QUESTIONS.md(§J authoring, §A/§B registration validation, §L signed-QR provenance, §F exposure window / per-poll registry, §K batch cadence, §C aggregation) and names the bridge that would close it. Includes an owner-gated acts table (the steps that must stay on the operator's side) and a proof-of-lifecycle table (which file proves which state at any moment)..github/ISSUE_TEMPLATE/poll-lifecycle.md+config.yml— a tracking issue whose checklist mirrors the pipeline one checkbox per step, so a poll's progress lives in the open. (No repo had issue templates before.)README.md,VISION.md— link the new doc.The doc is doc-only: it composes existing pieces and adds no behavior.
Verified (live walk)
data-pile/test/run.sh): build chain → verify → tamper-detect → owner decrypt → forward-only checkpoint proof all pass. (Signature checks skipped in this env — nossh-keygen.)tell/bin/qr, throwaway secret): token binds{pile, poll, round}— confirmed it differs by round and by pile.tell/test/landing.test.mjs):index.mdbuilds the prefilled Issue link with a parseabletellblock — passes.Companion PRs
One-line links to this doc in
data-pile,tell.anecdote.channel, andatlas.anecdote.channel(same branch).🤖 Generated with Claude Code
Generated by Claude Code