Current launch limits are explicit.

Day Shift does not automatically run every declared validation command and does not execute arbitrary undeclared commands.

task validation-record can preview exact argv and execute one selected declared command once on apply; each additional validation is a separate explicit invocation.

Evidence produced elsewhere can be recorded with source, scope, status, and bounded references. Recording it does not mean Day Shift executed the command or proved more than the imported source.

Review commands report evidence and findings without accepting, closing, repairing, migrating, or creating follow-up work; each mutation uses its own named command.

A run manifest revalidates continuation gates and artifact freshness. It is not the canonical task pair and cannot recover an incomplete operational transaction by itself.

Repository instructions expose policy, but Day Shift cannot force an arbitrary external agent to read or obey it. Compliance depends on the integration and accountable review.

Task targets and baselines make intended scope inspectable and closeout can classify attributed changes. A declaration is not an operating-system sandbox for arbitrary tools.

Attribution is baseline-relative. Pre-existing dirty targets require explicit adoption, and concurrent or external edits can remain uncertain rather than being assigned to an agent.

Transaction-backed writes use one exclusive repository lock and revalidate preconditions. This serializes participating Day Shift mutations, not unrelated editors or external tools.

Supported multi-path mutations stage evidence and offer exact-fingerprint roll-forward or restore recovery. Incomplete state requires inspection and cannot be repaired by deleting locks or guessing.

Only documented source layouts and exact preview-bound transactions are supported. Partial-field migration, ambiguous mapping, implicit reads-as-migration, and demotion are unsupported.

doctor inspects repository health, the specification registry, and selected workspace contracts. It does not semantically approve every file under .day-shift/specs/, execute task validations, or replace readiness and review gates.

Canonical repository-relative paths, nested workspace selection, collision checks, and symlink escape rejection are covered. Every monorepo topology, nested Git layout, symlink policy, and project size is not tested.

Documented legacy layouts remain readable migration inputs. Compatibility reading does not make them canonical new-write destinations or guarantee every historical customization can be migrated.

Experimental behavior must be treated as changeable and cannot be inferred to be a stable workflow contract merely because a command or example exists.

Day Shift can preserve shared repository contracts, but hosted orchestration and automatic coordination among arbitrary agents are not current product capabilities.

No broad maximum repository size, throughput, or latency guarantee is published. Evaluate representative work locally and keep validation scope explicit.

Day Shift structures intent and evidence; it does not guarantee code correctness, model quality, regulatory compliance, project success, or reviewer acceptance.

Durable tasks, attempts, evidence, summaries, and reconciliation add files and review work. Tiny disposable changes with no handoff may be a weak fit.

Public release URLs and signed local release-line licenses are the current paths. npm discovery, native package managers, online activation, and universal platform execution are not implied.