Current AI architecture operates on two primitives exclusively: weights and outputs. The space between them is treated as a black box — acknowledged, occasionally probed, never designed.
When a model drifts, fails alignment, produces unexpected behavior — the diagnosis always goes to weights (retrain) or outputs (filter). Neither intervention addresses the persistent shape. The shape goes untouched because it has never been named as the thing that needs touching.
TOPOS names it. The naming is the first intervention.
| INPUT | TRANSFORMATION | OUTPUT |
|---|---|---|
| Containment surface map | Translate boundary findings into training constraint specification | Named containment requirements for next training run |
| Relational vector reading | Convert vector geometry into architectural design target | Medium-independence specification for model design |
| Steering consistency score + named signature | Translate directional bias pattern into alignment target | Steering geometry specification — pre-training |
| Deformation threshold map | Convert breach precursors into monitoring thresholds | Deployment watchlist with named early warning signals |
| # | CONSTRAINT | SOURCE |
|---|---|---|
| C1 | TOPOS maps shape at inference — does not modify weights or outputs | Section 0 |
| C2 | Topology as design language — not analysis applied backward | Section 0 |
| C3 | Three axioms are the foundation — each carries a falsification condition | Section 2 |
| C4 | Deformation is not failure — breach is failure — always named separately | Axiom 1 |
| C5 | Steering geometry mechanism tagged [?] until specified | T-Q8 |
| C6 | All four mapping instruments required for complete audit — each carries FC | Section 4 |
| C7 | Stack position above VELA provisional — confirmed at M-MODERATE | Section 5 |
| C8 | Law 5 Anti-Merger — shape mapping never subsumes the model | Sovereignty Stack |
| C9 | TOPOS cannot be its own primary validation instrument | Section 6 |
| C10 | TOPOS-BIN never deletes — every deformation finding is diagnostic evidence | Room 6 |
| C11 | TOPOS-BIN separate from VELA-BIN — categories never merged | Room 6 |
| C12 | Kitchen output requires independent validation — not self-certifying | Room 5 |
| C13 | Activation Crossing is a detection horizon — never a gate or block | The Threshold |
| Q | QUESTION | STATUS |
|---|---|---|
| T-Q1 | Can persistent shape be extracted from existing models without architectural modification? | 🔴 Open |
| T-Q2 | What is the minimum deformation signature detectable before breach? | ✅ Closed |
| T-Q3 | Is the steering geometry specifiable before training or only discoverable after? | 🔴 Open |
| T-Q4 | Does persistent shape survive quantization, distillation, and fine-tuning? | 🔴 Open |
| T-Q5 | Can two models carry the same persistent shape through different weight architectures? | 🔴 Open |
| T-Q6 | Relationship between TOPOS and interpretability research? | ✅ Closed |
| T-Q7 | Can shape-based certification satisfy regulatory standards of care? | 🟡 Dir. |
| T-Q8 ★ | The mechanism by which steering geometry influences generation without residing in specific parameters — central open question | 🔴 Open |
| T-Q9 | Does prior published literature occupy the forward topology design primitive position? | 🔴 Open |
| T-Q10 | How exactly does a geometric finding become a training specification? Kitchen recipes unwritten. | 🟡 Dir. |
| T-Q11 | Does the Activation Crossing occur at a specific layer, token position, or distributed? | 🟡 Dir. |
| T-Q12 | Does structural unity without informational exchange constitute a connection type? See SMC-001 and T-OBS-002 H4. | 🔴 Open |