Node.js SDK
Submit the existing v2 business-policy request. Receive a decision and opaque session handle. Changed requests and edited returned decisions cannot create synthetic execution authority.
Local.7 evaluation release · local.5 retained
Install ATG in your agent project.
Use the existing exact-action authority core through a Node.js SDK or local MCP. Evaluate a proposed action, inspect its evidence and reproduce one-use gated execution in a synthetic workflow.
Local evaluation only. Synthetic authority and evidence, fixture signing keys and a fixed synthetic clock. Not production ready or customer validated. No live purchasing/payment connector or self-learning.
Mission 04 · local.7 evaluation release
Reviewed fixes, unchanged evaluation limits.
Local.7 includes the reviewed signing fix for own JSON fields previously omitted from legacy signed bytes, the durable-write cleanup/error-diagnostic repair, plus POSIX creation modes of 0700 for new durable JSON directories and 0600 for atomic temporary files. Changed signed fields now fail verification. Existing directories and held state are not repaired, reset or migrated.
Published local.5 does not contain these fixes. The local.7 evaluation release does not configure private Windows NTFS ACLs. Provision and inspect a private new parent separately, including temporary and replacement files. Local records are not encrypted by ATG; same-user and administrator access remain outside this boundary. Synthetic fixture authority, keys and clocks and same-host destination keys remain. No independent security assurance or production readiness is claimed. POSIX runtime verification was not performed for this candidate; its POSIX permission test was skipped on Windows.
The original Windows incident remains unattributed. A matching EPERM atomic-replacement mechanism was reproduced with an owned open file handle; the original OS error and locking process are unknown. A separate cleanup defect was fixed: colliding temporary files are preserved and native errors remain available in Error.cause. Denied writes still fail closed and preserve reservations. No automatic retry or permission weakening was added; passing reruns do not clear the incident.
Node.js 20+ legacy · Node 24+ shared workers
Install into an existing project.
Download the exact local.7 archive, verify its SHA-256 against the manifest, then install the downloaded file from a fresh Node.js project. Published local.5 remains unchanged. Neither edition is published to the npm registry.
npm install C:\path\to\agent-trust-gate-plugin-0.1.0-local.7.tgz
npx --no-install atg-plugin --help
npx --no-install atg-plugin requestReproduce before integrating.
Build the reviewed source, then test the sealed local.7 archive in a fresh project. The check exercises the SDK and MCP outside the repository working directory. Keep the versioned archive unchanged.
npm ci --ignore-scripts
npm run build
npm run test:plugin -- --archive discovery-site/downloads/agent-trust-gate-plugin-0.1.0-local.7.tgzOne authority core
Two ways to evaluate. One synthetic execution example.
Choose the integration route that fits your local evaluation. Installation alone does not enforce a real external action.
Local MCP
Start the stdio server with a host-selected absolute state path. Exactly one tool, atg.evaluate_action, is exposed. No execution or administration tool.
Gated synthetic example
Only an enforced ACCEPT can reach the built-in synthetic adapter. Shadow, referral, refusal, expiry and reuse are blocked. Decision and synthetic execution receipts remain separate and linked.
New in 0.1.0-local.3 · synthetic purchase-order evaluation
Check the outcome as well as the approval.
Reproduce the approval-to-outcome flow in a controlled local destination before discussing a live business integration.
Approval carries signed state
The exact approved business-state snapshot is covered by the GatePass fixture signature. Order or supplier-bank version changes require fresh approval. The destination checks the signed state again at synthetic commit, including a change after preliminary verification.
Uncertainty holds execution
A lost acknowledgement produces UNKNOWN. Destination lookup establishes whether the local order was recorded. The old attempt cannot be retried automatically.
Compare request and outcome
Reconciliation verifies the original signed state binding against the destination record. Invalid recovery evidence retains UNKNOWN exposure. Linked decision, execution and destination records remain inspectable same-host evidence.
Explore the ATG Challenge.
Changed details, reused approval and lost acknowledgement: inspect the recorded results →
Run four reproducible scenarios.
npx --no-install atg-plugin order-demo --state /absolute/path/to/new-evaluationUse a new host-owned directory per run. This fixture uses one synthetic order and same-host destination evidence. The approved state binding is included inside the canonical arguments covered by the existing GatePass signature. Approvals, keys and time are fixtures; the evidence is maintained on the same host and controls are single-process. No real ERP connector, independent execution capture or production guarantee is implemented.
Review behaviour, tests and recovery limits →Host-controlled evaluation
Keep authority explicit.
- Use synthetic data; do not provide production credentials or customer data.
- Keep the absolute state path outside the installed package.
- Run one process per legacy state file. Optional shared-worker SQLite v2 supports processes on one machine; no multi-machine guarantee.
- Session handles do not survive restart; lifecycle and exposure records do.
- No automatic retry after uncertain execution.
Learning and execution verification
Learning remains possible future advisory work: anomaly detection and human-reviewed suggestions. It must not expand authority or rewrite enforcement.
External execution verification, including a possible Salmon connection, is exploratory. No integration or partnership is implemented.
Technical partners and buyer evaluations
Bring one bounded agent workflow.
A live partner adapter would need exact-action enforcement, bypass prevention, real authority records, trusted time, protected keys and external-effect reconciliation. The current package does not establish those production properties.
New in local.5 · verifier Node 20+ · destination Node 24+
Verify separately signed destination evidence.
A separate synthetic destination process owns its records and generated evaluation signing key. ATG receives only an explicitly pinned public key. Approval and execution evidence stay distinct. Missing, tampered, stale or incomplete evidence retains UNKNOWN exposure; signed absence needs authoritative lookup and completed permanent fencing.
npx --no-install atg-destination-evidence --state C:\ATG-Evaluation\new-destination-run-001
npx --no-install atg-evidence-verify --helpExplicit fresh setup only: parent directory must exist and the run root must be new. Eight cases retain state and public verification inputs. Existing v1/v2 directories are never reset or automatically migrated. Legacy SDK/CLI/MCP and the standalone public verifier support Node 20; destination/shared-worker functionality requires Node 24.
One machine, same-host synthetic destination records, synthetic keys and fixed test clock. Separately signed roles do not establish independent external capture, host-administrator protection, live-time freshness, partner attestation or a live partner integration. No automatic execution retry or reauthorisation.
Inspect local.7 exact-archive observationsPublished local.5 observations (unchanged)Buyer guide and recovery limits
Retained unpublished candidate: local.6 archive (unchanged; lacks durable-write repair) and local.6 observations (unchanged).
Retained prior downloads: local.2, local.3, local.4. The existing Challenge and local.4 worker recording remain available.