# Private Companion Boundary

STRIX public core remains Apache-2.0 and simulator-first. Commercial,
customer-specific, evaluator-specific, or deployment-specific capabilities
belong in a separate private companion layer.

## Public Core

The public repository may contain:

- generic state estimation;
- task allocation;
- mesh coordination;
- simulation harnesses;
- explainability and replay;
- platform-agnostic adapter boundaries;
- neutral examples and public documentation.

## Private Companion Layer

The private companion layer is the correct place for:

- customer-specific scenarios and policies;
- evaluator collateral;
- operational playbooks;
- specialized adapters;
- private benchmark data;
- proprietary tuning, manifests, or release operations;
- commercial support and deployment material.

## Anti-Fork Posture

The durable protection is operational asymmetry:

- official release provenance;
- trademark and project identity;
- private companion modules;
- customer-specific tuning and support;
- managed updates;
- release manifests and signed artifacts.

Obfuscation and local checks can delay copying, but they are not the moat. The
moat is the maintained official line plus the private companion capability that
does not live in the public repository.