Goal Tracking Center

Run npm run check:goal-tracking and fix any schema or link failures.

Stage only scoped Goal Tracking OS files.

Keep generated view model and static page fresh from structured source records.

Handle deletions in a dedicated repository hygiene PR.

Use GitHub API or CLI only when approved and record results.

Core Goal Tracking OS documentation exists and is linked from the docs index.

Does not prove a live application runtime.

Keep docs synchronized with structured records.

File-backed non-LLM source records and validator exist for the Goal Tracking OS foundation.

Scoped validator is not a full public-readiness, release-readiness, or security-history scan.

Run npm run check:goal-tracking after every structured record change.

A generated static Goal Tracking Center page renders structured records without an LLM.

Does not prove routed app navigation, live GitHub state, deployment, public readiness, or release readiness.

Keep generated outputs fresh with npm run check:goal-command-center-view.

Pre-existing tracked deletions are outside this Goal Tracking OS slice and require dedicated review.

File deletion decisions require explicit approval.

Handle deletion recovery in a separate repository hygiene PR.

Live GitHub API/CLI inspection is external state and was not performed in this slice.

External GitHub API/CLI inspection requires explicit approval if policy requires it.

Inspect open and closed PRs in a dedicated GitHub governance pass.

Foundation validation is blocked by pre-existing deleted files and readiness dry-runs were not performed.

Deployment, release/tag creation, and public visibility changes require explicit approval.

Run readiness dry-runs only after repository hygiene is resolved.

Run npm run check:goal-command-center-view after source records change.

Define read-only scanner outputs in the next safe PR.

Record performed daily, weekly, or monthly reviews only when real current-period evidence exists.

SEIS-MS-001, SEIS-MS-002, SEIS-MS-003, SEIS-MS-004

Keep foundation records validator-backed and scoped to non-LLM evidence.

SEIS-MS-005

Decide restore, archive, replace, or approved removal for tracked deletions in a separate PR.

SEIS-MS-006

Define read-only scanner outputs after repository hygiene decisions are isolated.

Keep JSON source records schema-valid.

Regenerate the view after every source record change.

Prepare a repository hygiene review before staging deletion changes.

Run npm run check:goal-tracking after hierarchy edits.

Keep planning horizon, project, epic, and subtask panels generated from source records.

Do not stage tracked deletions in Goal Tracking OS commits.

Keep yearly scope connected to source records and avoid release/public readiness overclaims.

Resolve tracked deletion decisions in a dedicated repository hygiene PR.

Record a real monthly review only when current-month review evidence exists.

Run npm run check:goal-tracking after source record changes.

Do not stage tracked deletions or unrelated web/release drift in Goal Tracking commits.

Run npm run check:goal-command-center-view after source record changes.

Stage only scoped Goal Tracking files and keep tracked deletion decisions in a dedicated repository hygiene PR.

Prepare repository hygiene review before staging deletion changes.

Keep cadence and cycle records planned or active until dated review evidence proves a performed review.

Record performed daily, weekly, or monthly reviews only with current-period evidence.

Run the generator and freshness check after any source-record update.

Keep `npm run check:goal-command-center-view` in the scoped validation set.

npm run check:goal-tracking

The command passes and reports synchronized goals, evidence, execution, cadence, hierarchy, archive, cycle, risk, validation, view model, and static page records.

Run before every scoped Goal Tracking commit.

npm run check:goal-command-center-view

The generated view model and static page match the current structured source records.

Regenerate with `npm run automation:goal-command-center-view` when the freshness check fails.

scoped sensitive-pattern scan over Goal Tracking files

No secret assignment, key block, private path, file URI, or editor URI appears in scoped Goal Tracking files.

Keep scan output value-free and report only path/category if a finding appears.

Core Goal Tracking OS docs exist on this branch.

Does not prove a dynamic application runtime.

Backlog and PR queue define next safe Goal Tracking OS work and approval boundaries.

Does not inspect live GitHub PR state.

Product docs define the first non-LLM Goal Tracking Center view.

No routed Command Center app module is implemented.

Current branch has pre-existing unstaged tracked deletions that are not part of this slice.

Does not decide restore, archive, or deletion outcomes.

A local non-LLM validator checks required docs, strategic categories, goal records, evidence links, and execution records.

Scoped validator is not a full public-readiness or security scan.

A static non-LLM Goal Tracking Center view model and HTML page are generated from structured goal, evidence, and execution records.

Does not prove live GitHub state, routed app navigation, deployment, public readiness, release readiness, SSH, model-provider, benchmark, or dataset state. Does not resolve pre-existing tracked deletions.

Planned daily, weekly, and monthly review cadence records plus scoped completed, deferred, and follow-up ledger records validate without claiming that recurring reviews have been performed.

No recurring daily, weekly, or monthly review has been performed by this record. Does not resolve unrelated tracked deletions, public readiness, release readiness, live integrations, SSH, model-provider, benchmark, or dataset state.

Yearly, quarterly, monthly, weekly, project, epic, and subtask records are represented as file-backed Goal Tracking OS hierarchy data and validate through the local checker.

Does not prove a live project-management application, routed Command Center module, GitHub issue sync, deployment, public readiness, release readiness, SSH, benchmark, model-provider, or dataset state. Does not resolve unrelated tracked deletions.

Goal registry records include created_at, related_milestone, related_epic, last_reviewed, review_cadence, and notes fields validated by the local checker and surfaced in the generated view model.

Metadata values are foundation records and placeholders where review evidence has not yet been performed. Does not prove live project sync, recurring review completion, public readiness, release readiness, deployment, SSH, benchmark, provider, or dataset state.

Historical reference, repository hygiene review candidates, and deferred readiness claims are represented as archive ledger records separate from active official goals.

Does not perform archive cleanup, file deletion, public readiness dry-run, release dry-run, GitHub PR inspection, history rewrite, deployment, SSH, benchmark, provider, or dataset action.

Yearly goals, quarterly goals, monthly goals, and weekly priorities are represented as file-backed cycle records and validate through the local checker.

Does not prove a performed weekly or monthly review, live issue sync, public readiness, release readiness, deployment, SSH, benchmark, provider, or dataset state. Does not resolve unrelated tracked deletions or web/release sync drift.

Goal Tracking OS risk records and validation-step records are represented as file-backed ledgers and validate through the local checker.

Does not prove a full security scan, public readiness, release readiness, live GitHub state, deployment, SSH, model-provider, benchmark, or dataset state. Does not resolve unrelated tracked deletions or broader worktree drift.

Every tracked goal has an explicit roadmap-link record connecting it to roadmap, PR queue, and status references.

Roadmap links do not prove PRs were opened, merged, validated, or released. Does not resolve duplicate legacy backlog ids, unrelated tracked deletions, live GitHub state, public readiness, release readiness, deployment, SSH, model-provider, benchmark, or dataset state.

Resolve repo hygiene before public readiness dry-run.

Run release dry-run only after foundation recovery.

Create AI Core foundation docs after Goal Tracking OS records validate.

Keep the first surface non-LLM and evidence-backed.

Add AI model baseline docs before training.