# Atomizer Project Standardization Package

Date: 2026-02-18 UTC  
Owner: Manager (delegated to Tech Lead + Auditor + Secretary)

## 1) Technical Baseline (from Technical Lead)

### Scope
Define a minimum, enforceable baseline for Atomizer HQ so all agents/workspaces produce consistent, reviewable outputs across engineering, orchestration, and reporting.

### Standard Components
- Required identity files: `SOUL.md`, `IDENTITY.md`, `AGENTS.md`, `MEMORY.md`
- Required operational files: `HEARTBEAT.md`, `TOOLS.md`, `USER.md`
- Task tracking: taskboard transitions (`todo → in-progress → review/done`)
- Logging: append-only updates to `shared/project_log.md`
- Technical rigor: assumptions, units, BCs/loads, convergence, confidence in deliverables

### File/Folder Conventions
- Daily notes: `memory/YYYY-MM-DD.md`
- Durable lessons: `memory/knowledge/`
- Review records: `memory/reviews/`
- Shared coordination root: `/home/papa/atomizer/workspaces/shared/`
- Manager-owned status docs must not be directly edited by specialists

### Orchestration Contract
- Use `sessions_spawn` for scoped parallel/deep execution
- Use `sessions_send` for clarification, handoff, escalation
- Every specialist return follows:
  - `TASK:`
  - `STATUS: complete | partial | blocked | failed`
  - `RESULT:`
  - `CONFIDENCE: high | medium | low`
  - `NOTES: assumptions/risks/next validation`

### Acceptance Criteria
- Required files present and non-empty
- Taskboard updated at start/completion
- Deliverables follow structured result contract
- Shared log updated with timestamped outcome
- No policy boundary violations

## 2) Audit Standard (from Auditor)

### Compliance Checks
- Intake has scope + owner + deadline + mapped task ID
- Manager routing and correct specialist handoff
- Decision traceability via taskboard + `project_log.md`
- Protocol adherence (no review-chain bypass)
- Standardized outputs with assumptions/constraints/risks/repro notes
- Proper escalation for blockers

### Common Failure Modes
- Stale task status
- Missing explicit ownership
- Evidence-free claims
- Merge/release before audit pass
- Conflicting outputs left unresolved
- Wrong channel/result routing

### Evidence Required
- Taskboard transition history
- Linked artifacts (plan/logs/metrics/diffs/review note)
- Baseline vs final KPI table with units/constraints
- Audit log with severity and closure proof
- Final communication proof in designated channel/thread

### Approval Gates
1. Intake gate
2. Execution evidence gate
3. Audit gate (PASS or CONDITIONAL with closure)
4. Release gate (manager confirms critical/major closure)

## 3) Delivery Status
- Package assembled and published to shared workspace
- Team workflow pattern standardized for future projects
- Ready for CEO approval and enforcement