Known limitations
Day Shift is local Human-Agent-Contract workflow infrastructure. These technical boundaries help determine whether the current release fits a repository and execution environment.
Installation channels
Section titled “Installation channels”Public installation uses website-owned release URLs and platform installer scripts. Public npm discovery, Homebrew, winget, native package managers, .pkg, and .msi distribution are not current public install paths.
Environment compatibility
Section titled “Environment compatibility”Shell behavior, operating-system versions, repository layouts, dependency managers, security policies, automation hosts, and coding-agent integrations vary. Review installer output and task-specific validation rather than assuming every environment behaves identically.
Local and hosted boundaries
Section titled “Local and hosted boundaries”Normal CLI operation is local-first and offline-capable. Hosted collaboration, dashboards, and authenticated customer-service surfaces are not required for normal use and are not part of the current local CLI contract.
Workflow guarantees
Section titled “Workflow guarantees”Day Shift structures intent and evidence; it does not guarantee code correctness, model-output quality, regulatory compliance, project success, or reviewer acceptance. Humans remain responsible for reviewing changes and deciding whether evidence is sufficient.
Website-owned operations
Section titled “Website-owned operations”Release hosting, purchases, entitlement decisions, signed-file delivery, recovery, legal terms, warranty limits, and response policies remain on tnsds.tech. Documentation may explain how to use resulting artifacts but does not redefine those promises.