thanhnvandClaude Opus 4.8
36a4812ef3
Standard production layout: the OKR app (was nested under AINative_OKR_CASAN5/) is now
the repository root. No more wrapper directory.
- Promote AINative_OKR_CASAN5/* -> repo root (backend/ frontend/ packages/ apps/
.specify/ docs/ infra/ nginx/ scripts/ + configs). Merge tool dirs: .gitea (kept the
active deploy ci.yml, added harness-ci.yml + runbooks), .claude (agents/commands +
launch.json), .github moved up.
- Remove redundant: 00_SUBMISSION_PACKAGE, scattered root notes (FPT_CASAN_Full.md,
tu-tuong-casan.md, casan-tu-sinh..., casan_harness_assessment.md, source-review...,
README_CASAN5_REFINED.md), casan-next-plans/ and optimize-docs/ (competition/planning
artifacts — roadmap + design history preserved in git log / commit messages).
- Update all references to the old layout:
- .gitea/workflows/{ci,harness-ci}.yml, .github/workflows/{ci,deploy}.yml:
working-directory .; drop AINative_OKR_CASAN5/ prefix; .specify/{tests,scripts}
-> packages/casan-harness/... (.specify/logs state kept)
- .claude/launch.json, .gitea/*-runbook.md: path prefixes
- CLAUDE.md, README.md: docs/input -> apps/okr/domain/input
- policy-bundle.yaml: 8 policy paths -> packages/casan-harness/...; manifest re-signed
- secrets-scan.sh: fixture excludes -> new package/domain paths.
Full gate from the new root: PASS=64 FAIL=0 SKIP=3.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
895 B
895 B
Timestamp Protocol — MANDATORY
Every Timestamp: field in the boss log MUST use the real system clock.
How to get the real timestamp
ALWAYS run via the run tool immediately before writing any boss log entry:
Get-Date -Format "yyyy-MM-dd HH:mm:ss"
Use the exact output as the Timestamp: value. Never hardcode, estimate, or pre-calculate.
Incremental Writing Rule — ⛔ STRICTLY ENFORCED
BEFORE delegating to agent N:
1. Run: Get-Date -Format "yyyy-MM-dd HH:mm:ss"
2. Append [PROCESSING] STEP N entry to boss log
3. Delegate to agent N
AFTER agent N returns:
4. Run: Get-Date -Format "yyyy-MM-dd HH:mm:ss"
5. Append [PROCESSING] STEP N — COMPLETE entry
6. Proceed to gate check
⛔ PROHIBITED: Pre-writing multiple future step entries or writing the full boss log in one batch.