TEVM's declaration graph is active against the unpublished Flows source vendored as the vendor/flows submodule (built by scripts/factory/build-vendored.mjs on pnpm install), with bun and foundry pinned in mise.toml as the S.Mise layer. The exact source revision, install path, CLI/model pins, approval rules, and issue routes live in factory/policy.json; registry fallbacks are not supported.
WORKSPACE.ts, rootPACKAGE.ts, and package-localPACKAGE.tsfiles load through the real@smthrs/targetsAPI.pnpm factory:runtime-checkvalidates the full graph and approval refusals, then runs a model-freeAgent.Diffacceptance/write-set proof in an isolated workspace.//factory:checkexecutes policy, queue, intake, and declaration-type checks.smithers.d.tsis only an empty compatibility anchor and cannot mask missing APIs.- Package build, test, lint, typecheck, documentation, Cargo, conformance, parity, release, and deployment commands are represented as targets. Root compatibility aggregates call the established pnpm/Nx entry points where this Flows revision has no embedded query target.
- All coding lanes are
Agent.Diffcandidates. Deterministic gates run in the candidate loop;//:agentLintsruns after the accepted diff because agent targets cannot recursively gate other agent targets. //:mechanicalPrePushis the candidate-safe repository gate. Its wrapper runs daemonless, cloud-disabled Nx static analysis and hermetic tests sequentially with bounded parallelism. The sandbox allows local loopback servers but denies egress and receives no RPC secrets.//:externalIntegrationTestsis a separate maintainer boundary for the compiler CDN and live viem, MCP, and CLI RPC tests. Network access and the three integration variables are declared only on the package targets that need them.- Read-only issue intake and approval-gated issue settlement are checked-in GitHub workflows. The candidate job has no repository write credential; a protected
factory-approvalenvironment gates application of its exact hashed patch and PR creation. .smithers/UI.jsonis the strict local-desktop target surface.sites/contributoruses published@smthrs/uicomponents for presentation while every executable factory target continues to resolve from the unpublished local Flows checkout.
- Shell processes start at the repository root, including targets declared in nested packages. Nested declarations therefore use
scopedShell('<package>'), which rewrites package-local binaries and commands to the correct working directory;//factory:shellScopeLintrejects drift. Root/factory/scripts/test declarations remain explicitly workspace-relative. Runtime plans and focused executions still verify semantics the typechecker cannot see. - Package-mode
Agent.Prsettlement is unbound and approval-required targets have no durable local approval store. TEVM deliberately usesAgent.Diffplus the separate GitHub settlement job. Git.Commit,Git.Pr, and some renderer-only GitHub targets are declarations, not a substitute for an operator-approved outward action in this Flows revision..github/workflows/*.ymland the composite setup action are rendered by//.github:githubfrom.github/PACKAGE.tsand the workspace layers (pnpm/node, the Rust layer, the mise layer,//:vendorfor thegit submodule update --init -- vendorsetup step, and every secret a job's targets declare). The renderer still cannot express the factory's two-job environment/artifact boundary or artifact upload, so the factory workflows stay hand-authored and preserved, andparity-suites.ymlno longer uploads artifacts.- The Node runtime declaration reads the compatible
engines.noderange..nvmrc, factory policy, preflight, and CI setup jointly enforce the exact Node release.
pnpm factory:preflight
pnpm factory:check
pnpm factory:typecheck
pnpm factory:runtime-check
pnpm factory:ui-check
pnpm exec smthrs target //:mechanicalPrePush --no-cache
pnpm exec smthrs target //:externalIntegrationTests --no-cache
pnpm exec smthrs query '//...'
pnpm exec smthrs target //workflows/issue-to-pr:implementIssue \
--plan --input issue=123 --input type=bug --input approval=factory:readyThe authoritative contributor contract is AGENTS.md; operator setup and the issue lifecycle are documented in factory/README.md.
The PR-history evidence behind TEVM-specific lints and codegen lanes is recorded in factory/pr-history.md.