Skip to content

docs: Agentic 6-Phase Cadence + session-start bullet#271

Merged
dackclup merged 1 commit into
mainfrom
claude/sweet-fermi-G6bXt
May 27, 2026
Merged

docs: Agentic 6-Phase Cadence + session-start bullet#271
dackclup merged 1 commit into
mainfrom
claude/sweet-fermi-G6bXt

Conversation

@dackclup
Copy link
Copy Markdown
Owner

Summary

  • Refactors a user-shared research report (Master Prompt + 6 phase sub-prompts + CLAUDE.md template) into the existing doc surface — NOT a new .claude/skills/agentic-6-phase/, NOT a Master-Prompt artifact in-repo, NOT edits to any of the 18 subagent files. The report's underlying logic is already implemented in QuantRank's subagents + CLAUDE.md §Auto-routing; what was genuinely missing was a 6-phase mapping table a new session can scan in < 30 sec on top of the 9 phases.
  • WORKFLOW.md — new section "Agentic 6-Phase Cadence" between §"Tools You'll Use Daily" and §"Phase Overview". Mapping table (Step × Fire trigger × Subagent(s) × Done when) over Planning → Code Gen → Integration → Test → Deploy → Monitor + 5 cadence invariants. Reuses the standing 18 subagents only.
  • CLAUDE.md — new §Conventions bullet "Session-start phase identification" (~5 lines) pointing readers at PHASE_STATUS.md §"Current state" + WORKFLOW.md §"Agentic 6-Phase Cadence".
  • PHASE_STATUS_INFLIGHT.md — in-flight entry per PR docs(workflow): adopt PHASE_STATUS_INFLIGHT.md side-file (structural fix for parallel-PR collision) #237 side-file lockstep convention.

Numbers cited (verified vs PHASE_STATUS.md §"Current state" 2026-05-26)

Field Value Source
Schema (head) 0.10.5-phase4.5e PRs #264 + #265; cron #4 still at 0.10.4, next cron Wed 2026-05-27
Defense layer 33 declared = 7 vetoes + 26 annotates PHASE_STATUS.md line 21
Release tag v1.3.0-phase4.5e 2026-05-26 at 5db3b978
CVE baseline 15 open (0C/6H/7M/2L) After PR #194 patch + PR #226 triage

docs-reviewer verdict (2026-05-27)

NEEDS-CROSS-REF-FIX — both items applied in this commit:

  1. CVE attribution: "after PR #226 triage""after PR #194 patch + PR #226 triage" (PR chore(deps-npm): bump next 14.2.15 → 14.2.35 + postcss override (Phase 5, partial #41) #194 closed the 10 advisories; PR docs+agent: post-Dependabot-wave doc fixes (W1 FORM4_FETCH_SKIP + W3 literature-searcher injection guard) #226 documented the resulting state)
  2. Step 4 fire-trigger col: "Sections A-J""Sections A-L" (Section L added by PR feat(verify+auditor): OSAP factor-exposure proxy contract codification (closes #217 + #218) #221 OSAP proxy invariant)

All else passes: 4 cited numbers, 18 agent names, 3 cross-refs, token budget (WORKFLOW.md ≤ 1 page = 33 lines, CLAUDE.md = 5 lines), Rule 16 + Rule 18 no contradiction.

Out of scope (deliberately NOT done per user direction)

  • ❌ No .claude/skills/agentic-6-phase/ — overhead exceeds benefit (18 subagents ARE the per-phase prompts)
  • ❌ No Master Prompt / phase sub-prompts copied into the repo — they stay outside as reference card
  • ❌ No edits to the 18 subagent files
  • ❌ No AGENTS.md substance edit — cadence is Claude-Code-subagent-specific; INFLIGHT entry satisfies §Conventions lockstep

Deferred follow-ups

Test plan

  • ruff check . — N/A (no Python touched)
  • python -m compute.output.schema_check — N/A (no schemas touched)
  • pytest tests/ -m "not network" — N/A (no test surface)
  • docs-reviewer subagent — PASS after the 2 cross-ref fixes
  • Markdown-only diff (3 files, +116 lines additive)
  • Vercel preview — N/A (no frontend touched)
  • CI — expected green (lint + tests run unchanged paths)

Generated by Claude Code

…AUDE.md

Refactors a user-shared research report (Master Prompt + 6 phase sub-prompts
+ CLAUDE.md template) into the existing doc surface without creating a new
.claude/skills/agentic-6-phase/ skill. The report's underlying logic is
already implemented in the 18 subagents + CLAUDE.md §Auto-routing; what
was genuinely missing was a 6-phase mapping table a new session can scan
in < 30 sec on top of the 9 phases.

Scope (2 substance files + 1 INFLIGHT entry):

- WORKFLOW.md — new section "Agentic 6-Phase Cadence" between §"Tools
  You'll Use Daily" and §"Phase Overview". Mapping table (Step × Fire
  trigger × Subagent(s) × Done when) over Planning → Code Gen →
  Integration → Test → Deploy → Monitor + 5 cadence invariants. Reuses
  the 18 standing subagents — no new agent files. Session-start protocol
  cites schema 0.10.5-phase4.5e (PRs #264 + #265; cron #4 still at
  0.10.4, next cron Wed 2026-05-27 re-renders at 0.10.5), defense
  layer 33 declared = 7 vetoes + 26 annotates, tag v1.3.0-phase4.5e,
  CVE baseline 15 open (0C / 6H / 7M / 2L) after PR #194 patch +
  PR #226 triage.
- CLAUDE.md — new §Conventions bullet "Session-start phase
  identification" (~5 lines) pointing readers at PHASE_STATUS.md
  §"Current state" + WORKFLOW.md §"Agentic 6-Phase Cadence" using the
  standing 18 subagents.
- PHASE_STATUS_INFLIGHT.md — new in-flight entry per PR #237 side-file
  lockstep convention.

Out of scope (deliberately NOT done per user direction 2026-05-27):

- NO .claude/skills/agentic-6-phase/ — overhead exceeds benefit
- NO Master Prompt / phase sub-prompts copied into the repo
- NO edits to any of the 18 subagent files under .claude/agents/
- NO AGENTS.md substance edit — the cadence is Claude-Code-subagent-
  specific; cross-tool agents would route differently. INFLIGHT entry
  satisfies §Conventions "ship with every PR" lockstep.

docs-reviewer verdict (2026-05-27, agent id a2c87ed3679f55fe5):
NEEDS-CROSS-REF-FIX — both items applied in this commit:
1. CVE attribution: "after PR #226 triage" → "after PR #194 patch +
   PR #226 triage" (PR #194 closed the 10 advisories; PR #226
   documented the resulting state)
2. Step 4 fire-trigger col: "Sections A-J" → "Sections A-L"
   (Section L added by PR #221 OSAP proxy invariant; internal match
   with the same row's Done-when col)

All else passes: 4 cited numbers, 18 agent names, 3 cross-refs, token
budget (WORKFLOW ≤ 1 page, CLAUDE ≤ 5 lines), Rule 16 + Rule 18 no
contradiction.

Pre-existing SKILL.md schema-version table gap (rows for 0.10.5-phase4.5e
PR #264 + valuation_output_anomalous rename PR #265 missing) escalated
to schema-sentinel as separate doc-only PR per docs-reviewer recommendation
— not blocking on this scope.

Verification:
- ruff check . — N/A (no Python)
- python -m compute.output.schema_check — N/A (no schemas)
- pytest tests/ -m "not network" — N/A (no test surface)
- docs-reviewer subagent — PASS after the 2 fixes above
@vercel
Copy link
Copy Markdown

vercel Bot commented May 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
quantrank Ready Ready Preview, Comment May 27, 2026 8:05am

@dackclup dackclup marked this pull request as ready for review May 27, 2026 10:00
@dackclup dackclup merged commit 75b6c68 into main May 27, 2026
4 checks passed
@dackclup dackclup deleted the claude/sweet-fermi-G6bXt branch May 27, 2026 10:00
dackclup added a commit that referenced this pull request May 27, 2026
…commit) (#272)

First commit on `claude/phase-5-supabase-foundation` branch. Outline
draft per locked user direction (AskUserQuestion 2026-05-27):
- Phase slot A — Phase 5 = Supabase, ML push to Phase 6
- Sub-features 5.1-5.4 — Foundation + Auth + Watchlist + Alerts
  (NO comment — legal-risk-skipped on educational-disclaimer site)
- Wait-for-merge handoff after PR #271 cadence section landed

`phase-coordinator` Mode A verdict (agent id a0578bd4794157369):
PROCEED — no collision blocker; 3 skill gaps flagged for PLAN
acceptance criteria (Postgres↔TS lockstep / Route Handler security
cue / alerts observability Rule 18).

This commit ships ONLY the outline (~76 lines) at
`.claude/skills/phase-5/supabase-hybrid/PLAN.md`. Subsequent commits
on the same PR (5.0) will:
- Expand each sub-PR acceptance-criteria section after user approval
- `git mv` the 5 phase-5 ML stubs → phase-6/ + 3 phase-6 sentiment
  stubs → phase-7/ (per Mode A finding)
- Update 6 doc files in lockstep (CLAUDE.md / WORKFLOW.md /
  PHASE_STATUS.md / SKILL.md / AGENTS.md / README.md)
- Add PHASE_STATUS_INFLIGHT.md entry
- Update WORKFLOW.md:496-502 "Phase 5 foundational" → "Phase 6
  foundational" + SKILL.md Supabase library-matrix row label

Hard rules preserved per Phase 5 scope locks: composite formula
UNCHANGED (Rule 16) · Pydantic↔TS triple UNCHANGED (Rule 9) ·
static-export `output: 'export'` PRESERVED · ranking JSON pipeline
UNTOUCHED. Only ADD user-state surface on top.

License posture: Supabase Apache-2.0 ✅ · Resend free-tier OK.

Status: OUTLINE only — Draft PR will note this explicitly. No
review-ready expectation; awaiting user feedback on section structure
+ expansion priority + ToS sub-PR placement + auth provider list.

Co-authored-by: Claude <noreply@anthropic.com>
dackclup added a commit that referenced this pull request May 28, 2026
…v1.4.0 (#286)

* chore(docs): housekeeping PR-B — drain INFLIGHT + bump pointers post-v1.4.0

Phase B post-tag housekeeping. Drains 7 stale `(in flight, ...)` markers
from PHASE_STATUS_INFLIGHT.md (PRs #269, #267, #271, #280, #281, #282, #285)
to `(merged YYYY-MM-DD, <SHA>)`, and bumps stale schema/tag pointers
across CLAUDE.md / PHASE_STATUS.md / SKILL.md / WORKFLOW.md to reflect
the v1.4.0-phase4.6 release at `bbca9cac`.

Changes:
- CLAUDE.md §Phase status — schema `0.10.2-phase4.5e` → `0.10.7-phase4.6`,
  tag `v1.3.0-phase4.5e` → `v1.4.0-phase4.6` (2026-05-27, `bbca9cac`),
  "Recently merged" list refreshed from PRs #147-#154 → PRs #264-#285
- PHASE_STATUS.md §Current state — mirrored pointer bump; production-run
  pointer → `559c5269` (cron-#5 2026-05-27 chore commit); "Recently
  merged" prepended with 22 entries since v1.3.0, legacy list relabeled
  as "Earlier"
- SKILL.md schema-version table — 3 new rows: `0.10.7-phase4.6`
  (PR #283 release), `0.10.6-phase4.5e` (PR #269 GOOG/GOOGL per-class
  XBRL fix), `0.10.5-phase4.5e` (PR #264 multi-class CIK detector)
- WORKFLOW.md §Agentic 6-Phase Cadence Session-start protocol — pointer
  block bumped to current state
- PHASE_STATUS_INFLIGHT.md — 7 stale markers drained + new entry for
  this PR appended at end

AGENTS.md substance untouched per the existing delegation pattern
(line 372-375: "Canonical 'current state' lives in CLAUDE.md §Phase
status. Schema-version history table is in SKILL.md."). Cross-tool
agents reading state pull from CLAUDE.md as the source of truth.

Doc-only PR — `ruff` / `schema_check` trivially pass; no compute /
schema / scoring / valuation / frontend / Python / TS code change.

* docs(review-fix): docs-reviewer NEEDS-CROSS-REF-FIX — 3 items

Addresses 3 findings from docs-reviewer (sonnet) substance review of
the housekeeping PR (commit e060cb9):

1. PHASE_STATUS.md:98 — "v1.3.0 release tag" entry in §Next deliverables
   was stale (v1.3.0 shipped 2026-05-26, v1.4.0 shipped 2026-05-27).
   Replaced with forward-look for v1.5.0 gated on Phase 4.5e PR 5 +
   Issue #67 sector-CoE flip.

2. WORKFLOW.md:730 — Phase 4.5 historical task list trailing clause
   "v1.3.0 target pending release-captain ladder (LedgerCraft A-B
   series + this doc-refresh)" was stale. Replaced with the actual
   landing dates + SHAs for both v1.3.0 (5db3b97) and v1.4.0
   (bbca9ca).

3. docs/METHODOLOGY.md — annotate-only flag count out of sync with
   declared flags:
   - Line 16: "21 annotate-only flags" → "23 annotate-only flags"
   - Line 164: section heading "(21)" → "(23)"
   - Added 2 new bullets at end of §Annotate-only flags section:
     - `multi_class_aggregate_shares_suspected` (Issue #261 PR-A,
       PR #264) — CIK-collision detector; identity-equation check
       per Damodaran 2019 Ch. 16; no academic prior (data-quality)
     - `valuation_output_anomalous` (Issue #262, PR #265) — Site-2
       output-anomaly detector renamed from `data_quality_input_corruption`;
       no academic prior (data-quality); semantic distinction from
       Site-1 input-corruption veto documented inline

Both new METHODOLOGY entries are data-quality detectors with no new
academic claim — `multi_class_aggregate_shares_suspected` cites the
existing Damodaran 2019 anchor (already in the file) for the
per-class market-cap identity equation, and `valuation_output_anomalous`
is the renamed Site-2 emission of the existing `data_quality_input_corruption`
defense. Neither requires methodology-scientist verdict per the
"Internal — data-quality" pattern shared with `goodwill_heavy` /
`data_quality_input_corruption` Site-1 already in the section.

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants