SYSTEM BOUNDARIES
Tinlyt is one component in a governed system of systems. Integration design must preserve the responsibilities of each canonical service.
Owns consequential execution authority, identity, authorization, policy, approvals, secrets, budgets, audit and governed tool registration. Tinlyt must not create a parallel authority plane.
Repository integration recorded; deployed policy not certifiedOwns orchestration and lifecycle concerns such as workspaces, sessions, tasks and memory. Recurrence policy and budgets remain with the designated orchestration owner.
Live lifecycle integration requires target-environment proofProvide the developer/artifact plane and typed client contracts. Integration should pin exact supported revisions and test the same consumer versions used by deployment.
Contract revisions must be revalidated for each releaseRemains the system-of-systems conformance authority. Passing local tests or having an adapter does not substitute for conformance evidence on the intended revisions.
Deployment-specific conformance not certifiedReceives structured intelligence through an explicit ingestion contract. Entity identity, event semantics, provenance and idempotency must remain consistent end to end.
Live authenticated ingestion remains unverifiedRepository adapters and CI can demonstrate code-level compatibility. They cannot prove live credentials, active policies, deployed tool registration or successful production ingestion.
Developer guidance