AI Foundry Desk 0.4.0 — One project policy, consistent agents
AI Foundry Desk 0.4.0 — One project policy, consistent agents
AFD 0.4.0 helps you replace a collection of drifting, agent-specific instruction files with one
reviewable project harness. Codex, Claude Code, Pi, and other selected agents can share the same
project policy without maintaining several copied versions of it.
See the problem before changing the project
afd harness audit inventories the repository without writing to it. It shows which policy is
canonical, which agent files are pointers or independent instruction sets, where instructions are
duplicated, and which discovery claims are not yet verified.
The resulting plan is available in a concise human view or structured JSON. Every proposal is bound
to the exact policy content, Git revision, and visible workspace state, so a reviewed decision cannot
quietly drift onto a newer project state.
Review a real proposal, not a promise
AFD generates minimal adapters that point to the canonical policy rather than copying its rules.
You can render them into an external staging directory and inspect every proposed creation, managed
update, or legacy removal without touching the repository.
If an existing agent file contains distinct project-owned guidance, AFD preserves it and blocks the
definitive apply. You decide how that guidance should be reconciled; AFD does not discard it.
Test every selected agent before apply
The live harness test builds a disposable policy-only workspace and starts fresh, bounded,
read-only sessions. Each selected agent must independently identify the same canonical policy and
return the same fingerprint. Missing commands, unsupported safety contracts, inconsistent behavior,
timeouts, or write attempts fail the gate instead of being silently skipped.
Apply with evidence and keep a way back
Applying a harness requires both the exact reviewed plan token and its matching passing live test
evidence. The update is transactional, followed by hash and workspace verification, and recorded in
a private per-user receipt outside the project.
Rollback is equally scoped: it refuses a project that has drifted since apply, restores the exact
prior bytes, and records what was restored. Conservative cleanup can remove proven redundant thin
pointers such as an unnecessary AGY.md, but never removes a file based on its name alone.
A practical, incremental workflow
- Audit the repository.
- Review or externally stage the exact plan.
- Run the disposable multi-agent test and save its evidence.
- Confirm the plan token to apply.
- Verify the result or use the receipt for exact rollback.
The workflow and agent coverage are documented in docs/PROJECT-HARNESSES.md. Installing or
upgrading AFD still does not apply workstation layers, start telemetry, or modify a project.
Windows x64 remains the fully validated environment. The checksum-verified portable CLI bootstrap
remains available for the documented POSIX path; macOS support is experimental.