Incorporation system
How external extension capabilities enter Torsionfield without architectural drift or license confusion.
Four strategies
| Strategy | Use when | Result |
|---|---|---|
| Direct integration | License and architecture permit source reuse. | Attributed code normalized behind Torsionfield contracts. |
| Clean reimplementation | Behavior is valuable but source terms conflict with distribution goals. | Independent implementation from public behavior and fresh tests. |
| Format compatibility | Users need import/export or interoperable artifacts. | Parsers and writers without incorporating runtime code. |
| Isolated bridge | An external tool should remain separately installed or licensed. | Typed process/MCP/native-messaging boundary. |
Admission gates
- Capability must provide a measurable user gain.
- Source revision and license are pinned.
- Overlap with existing primitives is mapped.
- One shared Operation Graph is preferred over a parallel engine.
- Every effect receives operation identity and postcondition evidence.
- Update extraction and rollback are defined before merge.
No automatic code laundering. Model-assisted extraction never overrides copyright or license obligations. The provenance ledger records whether code, behavior, formats or only ideas were incorporated.