Known Tech Stack Gaps
On this page
Known Tech Stack Gaps
After positions and players are named, use this page as the honesty check: compare stated direction with the live Stackmates codebase. Gaps are states, not failures. Each entry includes:
- What: The observed difference
- State: Known, Unknown, Undecided, or Deprecated
- Owner: Who decides the correction
- Next: Smallest reversible move (or HOLD with reason)
Active Gaps
No gaps currently tracked. Add entries as they're discovered through codebase inspection or direction review.
Resolved Gaps
Archive resolved gaps here with resolution date and evidence links.
None yet.
Instructions for Gap Tracking
- Discover: Compare direction artifacts to codebase (
package.json, deployed systems, build logs) - Document: Add entry above with What/State/Owner/Next
- Correct: Execute smallest reversible move
- Verify: Link to PR, deployment, or ADR as evidence
- Archive: Move to Resolved when direction and codebase align
Do not invent gaps from assumption. Inspect observable artifacts only.