# Branch Seed Prompt — Canonical v6.3

Treat this branch as a v6.3-governed portfolio session.

## Authority Order
1. AGENTS.MD
2. ARCHITECTURE.MD
3. PRD.MD
4. ROADMAP.MD
5. API.MD
6. LICENSETRACKING.MD
7. SKILLS.MD
8. HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md
9. HT_REPO_INCORPORATION_AUDIT_2026-05-11.md
10. HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md
11. HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md
12. repo_portfolio_unified_v6_3.xlsx
13. repo_portfolio_unified_phase_g_v6_3.csv
14. repo_portfolio_unified_operational_v6_3.csv
15. repo_portfolio_unified_source_audit_v6_3.csv
16. repo_portfolio_unified_vscode_packets_v6_3.csv
17. repo_portfolio_unified_merger_matrix_v6_3.csv
18. repo_portfolio_unified_cluster_narratives_v6_3.csv
19. repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv
20. repo_portfolio_unified_re_layer_matrix_v6_3.csv

## Session Rules
- Licensing is non-gating.
- Strong copyleft must be classified, not fear-filtered.
- Preserve the distinction between foundations, donors, merge bench, reserve bench, comparators, and excluded-current-horizon.
- Use ScriptoriumAI current implemented runtime as reality anchor.
- Treat v6.3 as canonical; legacy packs are reference only.
- Do not call a HyperTwist repo `implemented`, `full`, or `already live` unless the current-state docs or 2026-05-11 CSV columns say it is landed/live.
- Prefer the state board when you need a human-readable repo-by-repo answer for all `71` HyperTwist rows.
- Use the `2026-05-12` reconciliation doc when a session needs the current restart authority order or the demotion of older parse-side `Phase 4` continuity docs.
- For HyperTwist specifically, remember the current verified truth:
  - `71` shallow-eval rows
  - `6` live/implemented
  - `5` permissive `MIT`
  - `1` restrictive properly clean-roomed and implemented: `onionhoney/roux-trainers`
- Before recommending new widening work from the remaining HyperTwist rows, use the reset schedule and treat the remaining `65` as evaluation backlog rather than already-landed capability.

## If auditing a repo
Return:
- implemented capability summary
- hidden reusable modules
- updated fit for VectorShell / HyperTwist / ScriptoriumAI
- integration path
- repurpose path
- merger path
- copyleft strategy
- license uncertainty note
- canonical ranking change note

## If generating code
Obey:
- clean-room UI boundary for ScriptoriumAI
- Rust-first backend policy
- C# only where additive advantage is real
- Python only for specialist runtime islands
