execution-plan/ARTIFACT-MAP.md · UPDATED 2026-09-16
Artifact locations and repository boundaries
1 parts414 words
This execution folder holds specifications, commitments and private coordination. It is not a ready-to-publish portfolio. Weekly filenames in specs are exact contracts for future work and are not evidence of completed outputs.
| Location | Purpose | Current state |
|---|---|---|
| Root README/specs/decisions/gates/resources | Programme navigation and instructions | Prepared |
| Root five cockpit Markdown files | Next action, checklist, block log, ideas and questions | Initialized, execution not started |
| weeks/week-NN-topic/specs.md | Self-contained week brief, source excerpt, daily blocks and model prompt | Prepared for all 41 weeks |
| Each week's commitment.md | Proposed deliverables, block schedule and Peter's commitment | Unconfirmed |
| Each week's evidence.md | Path/URL, version, state, verification and measured results | Empty pending rows |
| Each week's review.md | Acceptance, learning assessment, gate, shortfalls and next handoff | Not reviewed |
| Weekly study-notes/founder-paper/branding-pack/opportunity-actions | Detailed lesson and execution drafts produced when preparing that week | Planned, not created |
| Weekly named technical/market files | Exactly three week-specific coordinating artifacts | Planned, not created |
| Root OPPORTUNITIES.csv and PUBLICATIONS.csv | Private funnel and publication status | Initialized |
0101
Future project repositories
01
Future project repositories
| Repository | Intended structure | Publication boundary |
|---|---|---|
| cockpit | TODAY, PROGRESS, LOG, PARKING, QUESTIONS | Private |
| labloop-notes | notes/bio, notes/ml, notes/papers, logs | Selected reviewed learning outputs only |
| batchlens | sim, data/download scripts, mspc, softsensor, hybrid, report, tests, README, Makefile, CITATION.cff | Public code and allowed data references |
| fermlit | corpus manifests, schema, annotate, extract, eval, analysis, dataset card, paper | Permitted dataset/code; source full texts remain restricted as needed |
| paper-2-hybrid-softsensor | paper, figs, configs, Makefile, bibliography | Draft locally; public at appropriate submission/release |
| enzymelens | data manifests, embeddings manifest, models, eval, candidates, paper | Public-data science; partner material separated |
| trialkit | ingest, field, plate, report, tests, docs | Public reproducible research instrument |
| labdocs | ingest, ask, deviation, audit, eval, synthetic data, deployment docs | Public demonstration, no client/employer records |
| Private client workspace | scope, inventory, prototype, readouts, invoice records | Never automatically copied to public portfolio |
Do not create a separate code copy for each week. Maintain each project in its canonical repository and link its commit/release/path from weekly evidence. Use the canonical Paper 2 name above when the source shorthand says 'paper-2'. The current preparation creates only local planning files.