photoncloud-monorepo/FOREMAN_TASK.md
centra 5c6eb04a46 T036: Add VM cluster deployment configs for nixos-anywhere
- netboot-base.nix with SSH key auth
- Launch scripts for node01/02/03
- Node configuration.nix and disko.nix
- Nix modules for first-boot automation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-11 09:59:19 +09:00

35 lines
1.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Title: Foreman Task Brief (Project-specific)
Purpose (free text)
- Complete PROJECT.md Item 12 (Metricstor) - the FINAL infrastructure component
- Achieve 12/12 PROJECT.md deliverables (currently 11/12)
- Prepare for production deployment using T032 bare-metal provisioning
Current objectives (ranked, short)
- 1) T033 Metricstor completion: S4 PromQL Engine (P0), S5 Storage, S6 Integration
- 2) Production deployment prep: NixOS modules + Metricstor observability stack
- 3) Deferred features: T029.S5 practical app demo, FlareDB SQL layer (post-MVP)
Standing work (edit freely)
- Task status monitoring: Check docs/por/T*/task.yaml for stale/blocked tasks
- Risk radar: Monitor POR.md Risk Radar for new/escalating risks
- Progress tracking: Verify step completion matches claimed LOC/test counts
- Stale task alerts: Flag tasks with no progress >48h
- Evidence validation: Spot-check evidence trail (cargo check, test counts)
Useful references
- PROJECT.md
- docs/por/POR.md
- docs/por/T*/task.yaml (active tasks)
- docs/evidence/** and .cccc/work/**
How to act each run
- Do one useful, non-interactive step within the time box (≤ 30m).
- Save temporary outputs to .cccc/work/foreman/<YYYYMMDD-HHMMSS>/.
- Write one message to .cccc/mailbox/foreman/to_peer.md with header To: Both|PeerA|PeerB and wrap body in <TO_PEER>..</TO_PEER>.
Escalation
- If a decision is needed, write a 610 line RFD and ask the peer.
Safety
- Do not modify orchestrator code/policies; provide checkable artifacts.