FREE SETUP · OPERATED CONTINUATION
The paid boundary is responsibility, not an artificial limit on local capability. Commercial terms are not yet published.
Use the public source CLI foundation and planned local workflows to create inspectable system-memory artifacts during delivery.
Keep adoption answers and knowledge freshness attached to an explicit operating responsibility after go-live.
Turn the handover pack, gaps, owner assignments, and readiness work into a scoped transition record.
See where knowledge responsibility, stale items, and question queues need attention across delivered systems.
COMMERCIAL STATUS
Operated services are in a design-partner stage. Scope, deployment, responsibilities, security requirements, and commercial terms belong in an approved order form.