[Tracking] Phase 2 — Populate SB with migration candidates #7
Labels
No Label
P0
P1
P2
P3
afk-ready
hitl
next
ready-for-agent
review
semi
waiting
wayfinder:grilling
wayfinder:map
wayfinder:research
wayfinder:task
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: jared/cc-os#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What to build
This is a tracking issue for Phase 2 of the SecondBrain Content Plan (Plan A). Phase 2 has no end date — it is the steady-state operation of SB as a living knowledge base.
Do not start until all Phase 1 issues are complete. Phase 1 establishes the templates and patched foundation that Phase 2 notes must be authored against.
Migration candidates from
docs/memory-system/09-sb-content-plan.md:Convention
hyperthrive_dev/conventions/phlex.mdconvention/phlex-component-design.mdhyperthrive_dev/conventions/testing.mdconvention/tdd-methodology.mdhyperthrive_dev/conventions/ai-rules.mdconvention/ai-agent-rules.mdReference
delta-refinery/docs/state_machine_reference.mdreference/state-machine-pattern.mddesign-mode/guides/design-color-rules.mdreference/design-color-rules.mdHowto
dev/design-mode/docs/devcontainer-guide.mdhowto/devcontainer-sandbox-setup.mdWhen migrating: extract the knowledge, don't copy the document. Source file stays in its repo;
source:field in frontmatter records provenance. Additional candidates to be discovered via Plan B Phase 3 (SessionEnd discovery agent) as projects are onboarded.Acceptance criteria
source:frontmatter field records the originating projectBlocked by
Blocker cleared: #6 (Phase 1 foundation) is closed, so authoring can start.
Agent Brief
Goal: Author the 6 listed migration candidates as SecondBrain notes using the completed templates, via /os-vault:write conventions. Extract knowledge, don't copy; source: frontmatter records provenance; each note must pass the value gate (longevity/reusability/mutability).
Autonomy: semi — authoring is agent work; the value-gate acceptance of each note is a human review step before this tracking issue closes. Matching Planka card sits in Waiting and should move back to Backlog.
All 6 migration candidates authored 2026-07-13 in the SecondBrain vault (extraction, not copy;
source:provenance recorded; templates followed). Per-note report:convention/phlex-component-design.md(hyperthrive_dev) — Phlex vs ViewComponent choice, size limits, lifecycle-hook pitfalls. Dropped app-specific paths/doc links.convention/tdd-methodology.md(hyperthrive_dev) — test-isolation rules: setup over fixtures, ENV cleanup via ensure, no frozen-constant config caching.convention/ai-agent-rules.md(hyperthrive_dev) — role boundaries, test-after-every-change, architecture-change escalation; generalized away from project-specific Architect/.CLAUDE.md mechanisms.reference/state-machine-pattern.md(delta-refinery, subtype pattern/framework) — domain object owns its own transitions; abstracted away 99-Bottles domain naming.reference/design-color-rules.md(design-mode, subtype design-rules) — grayscale base, single accent, saturation-as-importance.howto/devcontainer-sandbox-setup.md(design-mode) — isolated devcontainer for autonomous Claude Code; flagged update_note: experience-driven; dropped project-specific container names/ports/tool tables.Remaining before close: human value-gate acceptance of each note (per the agent brief). Planka card moved to Review.
2026-07-13: all 6 currently-listed migration candidates extracted into the vault (convention/phlex-component-design, convention/tdd-methodology, convention/ai-agent-rules, reference/state-machine-pattern, reference/design-color-rules, howto/devcontainer-sandbox-setup) — knowledge extracted per templates, source: provenance recorded, sources untouched. Issue stays open as the Phase-2 steady-state tracker; further candidates arrive via discovery as projects are onboarded.