Skip to content
Donovan Worrell edited this page Oct 26, 2026 · 2 revisions

Execution board: https://github.com/dlworrell/code-noodling/issues/75

Project log: https://github.com/dlworrell/code-noodling/discussions/76

code-noodling: purpose, local work and delivery phases

Current work gate: Phase 2 of 5 — Engineering foundation. Current phase is the first gate still requiring evidence. Implemented capabilities beyond that gate remain recorded in the source; this is not a percentage-of-code estimate or a new AES certification.

Purpose and authority

Contains governed crypto and election scopes plus prime/dice research; implemented experiments retain explicit scientific and security limits.

Owner repository: dlworrell/code-noodling. Catylist inventory class: experimental. Repository code/specifications/ADRs remain authoritative; Wiki and Discussions are coordination views. Purpose source: README at the inspected revision, Git blob 0136ee12944757af7935d1033a6ff17b7fb151b3.

Phase graph

flowchart LR
  P1["1. Purpose and scope"]
  P2["2. Engineering foundation"]
  P3["3. Bounded implementation"]
  P4["4. Verification and recovery"]
  P5["5. Release and operation"]
  P1 --> P2 --> P3 --> P4 --> P5
  classDef done fill:#d7f5dd,stroke:#257d3e
  class P1 done
  classDef active fill:#fff1b8,stroke:#9d6b00
  class P2 active
Loading

Phase exit evidence

Phase Evidence needed to clear the gate Current disposition
1. Purpose and scope Source-backed purpose, ownership, bounded scope and unresolved mission decisions recorded Observed in the linked source
2. Engineering foundation Repository identity/manifest, adopted applicability, verified publication, useful CI and traceable local work Open: reconcile the repository-specific gaps below
3. Bounded implementation One supported vertical slice and reproducible build/use contract Retain existing implementations; reconcile the selected slice's evidence
4. Verification and recovery Functional/negative/security evidence, provenance and restore/rollback exercise Open until exact-subject evidence is linked
5. Release and operation Owning release decision, supported limits and durable operating documentation Not inferred from a passing build or this planning record

Next bounded work

  • 1. Enforce the requested November 3, 2026 election start gate for each state, one hour after its official last poll closing, with boundary tests.

Planning slice: 30–60 minutes. Acceptance: a reviewer can follow the resulting source change or retained evidence from its exact commit, reproduce the stated fixture/report, and see every remaining unknown. Split the slice if its implementation exceeds that allowance.

  • 2. Reconcile the already-merged crypto provenance steps with the two remaining real-fork/wrong-workflow evidence cases.

Planning slice: 30–60 minutes. Acceptance: a reviewer can follow the resulting source change or retained evidence from its exact commit, reproduce the stated fixture/report, and see every remaining unknown. Split the slice if its implementation exceeds that allowance.

  • 3. Prepare one prime/dice scope-migration fixture preserving existing file identities and the 22 retained security dispositions.

Planning slice: 30–60 minutes. Acceptance: a reviewer can follow the resulting source change or retained evidence from its exact commit, reproduce the stated fixture/report, and see every remaining unknown. Split the slice if its implementation exceeds that allowance.

Existing repository work

No existing open repository issue was returned at capture; this board creates the local execution anchor without inventing completed work.

Cross-repository parent: Catylist #28. Crypto remains unfinished and not cleared for secrets. Election reports retain their experimental statistical limits.

Coordination and updates

Use Issues for executable tasks and defects; use Discussions for purpose clarification, decisions under review and progress explanations; use the Wiki as the maintained navigation and evidence index. Link existing specifications and ADRs instead of copying competing normative text. Update this record after a verified source change, not merely after a chat claim. Record the exact PR/merge, test or artifact, current phase and next work gate. Preserve human-owned priorities and historical source links. Donovan reviews/approves from iOS. Agents produce verified commits and complete authorized merges. No desktop, Working Copy or second signing pass is a dependency for agent-created work.

PM method: the requested Dropbox Senior Project Manager prompt, applied to the repository's actual stack and source. Its website-specific framework examples are not imposed on these projects.

Verified election collection gates — October 25, 2026

code-noodling #77 is merged at verified 81909615e6d2b21d68f73dbe6a034de812489162. Its single PR commit is verified and all applicable hosted checks passed. The deployed Election Source Watch run passed all 70 watcher tests and held all three states before pending lookup, collection and publication.

State Earliest live collection on November 3, 2026 local time UTC on November 4
Maine 21:00 EST 02:00
Washington 21:00 PST 05:00
Alaska statewide 21:00 HST in Adak / 22:00 AKST in Anchorage 07:00

The state-specific guard precedes all source discovery/downloads and applies to manual and forced collection. A simulated clock is allowed only for offline status. The workflow can still launch offline validation before election night; its live/publication commands remain held. The source-linked operating table records the scheduled poll-closing basis and limits. Historical analysis and remaining scientific/crypto qualification retain their existing dispositions.