Read .github/github-instructions.md and Software-Requirements-Document.md before changing the agent layer. Treat the SRD open questions as unresolved until a stakeholder answer is recorded; never replace a # TODO [Qn] with an assumption. The active Milestone 1 replacement is deployed as ai-transfer-agent version 8 in East US 2 under fsi-wt-dev; prior North Central US version 6 is retained as historical deployment evidence. Its immutable audit system of record is WORM Blob only. Do not add SQL, Fabric, Cosmos DB, live ACATS submission,…
Avoid creating new Markdown (.md) files as part of routine work. Prefer updating existing documentation, subject to the README restrictions below. Only add a new document when explicitly requested by the user or when it adds clear, lasting value that existing documentation cannot cover. Do not create summary, planning, progress, or implementation-note Markdown files unless requested. Do not add README.md files inside source folders. This repository has one root README.md. Document code in TSDoc on the declarations themselves. Do not…
Read README.md for the human-facing, agent-first introduction, REFERENCE.md for commands/setup/schema, and DESIGN.md for architecture and evidence boundaries before changing behavior. This is a C#/.NET 10 tool for TLA+, Dafny and P source/model evidence, not a bundled agent or hosted AI service. Design and document it around the C#/.NET toolchain: Roslyn source resolution, explicit C# compiler context, and build/execution evidence. Formal backends complement that focus; do not present the tool as language-agnostic or imply support for other implementation languages. Keep shared…
This file gives an AI coding agent everything it needs to turn a multilingual evaluation benchmark paper into a complete, schema-valid contribution under data/benchmarks/<BenchmarkName>/, following CONTRIBUTING_BENCHMARKS.md. Invoke this workflow whenever the user gives you a benchmark paper (PDF, URL, arXiv/ACL ID, or pasted text) and asks you to add/extract/register it as a Vibhasha benchmark. Ask the user only if these are missing: Do not proceed on a title/abstract alone — you need the full paper (methodology, data collection, and annotation…
This repository publishes the LTG243 Fabric-only demo. The deployable source is the synthetic data under data/, the Fabric item definitions under src/fabric/, and the two root deployment entry points. - Read instructions/README.md before running deployment commands. - Use Node.js 24 or later and the exact Fabio version pinned in .fabio-version (0.79.0). Upgrade with fabio upgrade --target-version 0.79.0 if needed. - Keep data/scenario.json frozen. Do not hardcode values already defined by the scenario. - Generated output must remain deterministic. Do not…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read docs/VISION.md and docs/contracts.md, then the exact local interface needed for the next outcome. Shared promises live in the Constellation boundary and shared agreements; link them rather than copying them into local guidance. Use Converge for ownership, changes and verification. Keep local agreements focused on this component's contribution. Exact APIs, schemas and tests remain authoritative in their technical homes. Current…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Use Converge and the umbrella shared agreements. Read this vision and the local boundary for the next outcome. Keep shared promises in the umbrella and exact Slack interfaces in their serving technical documents. Inspect current implementation and relevant evidence; do not maintain a parallel feature, release or gap inventory. Admin pages do not define future product UX. Coordinate changed shared…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Use Converge and the umbrella shared agreements. Read this vision and the local boundary for the next outcome. Keep shared promises in the umbrella and exact Teams interfaces in their serving technical documents. Inspect current implementation and relevant evidence; do not maintain a parallel feature, release or gap inventory. Admin pages do not define future product UX. Coordinate changed shared…
Read these before your first edit. They apply to every session working here — human, Amplifier, or another tool's coding agent — and they are the same rules the people here follow. Nothing on this page needs the Amplifier bundle. Read next: PINS.md (hard facts), docs/CONTRACTS-README.md (what a contract is and how to change one). New to this method, or taking it to another repository? docs/ADOPTING.md is the first day start to finish — install, check that it took, start…
Converge toward the vision. Never edit a locked contract directly; write a proposal beside it as <contract>.vN-candidate.md and stop. The conformance ledger is at docs/LEDGER.md. Run the kits with uv run conformance/<name>/run.py ..
Own the portable image capability, its module, skill, context and composition. Keep application setup, UI/artifact presentation and live account qualification in the consuming host. Runtime code must not depend on…
This repository owns portable Work composition, operating instructions, and composition tests. Keep runtime implementations in their module repositories. Application-specific setup, browser acceptance, and preview launchers belong in the consuming application. Do not add a dependency on an application here. Reusable behaviors must preserve both the host's orchestrator and context manager. Complete roots/session compositions choose defaults; applications may override them. work-local is transcript-only; work-session owns both runtimes. work-amp-dev composes Work plus Foundation's amp-dev behavior, never Anchors. Preserve @work:context/system.md explicitly in each…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read docs/VISION.md, contracts/README.md, docs/compatibility.md and docs/contract-assessment.md before changing product behavior. Use docs/architecture.md and docs/ux-contract.md for implementation detail. Amplifier is the app; Tempo is its optional companion. Keep implemented behavior and future workspace/device capabilities clearly separated. Run meaningful core/native checks for behavioral changes and release-tool tests for packaging/publication changes. Native acceptance requires macOS; fixtures do not establish focus, notifications, signing or…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read the vision, then select the relevant boundary from the contract map. Shared promises and collaboration practice live in the Constellation umbrella; apply them without copying a second methodology or family contract here. Inspect current source, configuration and meaningful checks for the next outcome. Preserve exact protocol definitions in their existing homes. Guides and the bundled administration client add no…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read docs/VISION.md and docs/contracts.md, then the exact local interface needed for the next outcome. Shared promises live in the Constellation boundary and shared agreements; link them rather than copying them into local guidance. Use Converge for ownership, changes and verification. Keep local agreements focused on this component's contribution. Exact APIs, schemas and tests remain authoritative in their technical homes. Current…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read the vision, then select the relevant boundary from the contract map. Shared promises and collaboration practice live in the Constellation umbrella; apply them without copying a second methodology or family contract here. Inspect current source, configuration and meaningful checks for the next outcome. Guides explain contracts and add no separate commitments. Keep release history, private deployment evidence and a…
The core package must not import Amplifier CLI, Amplifier Converge, provider SDKs, or host adapters. Optional application integration belongs under adapters/. Preserve ordinary finite execution when the host supplies no live runtime. Preserve input/call/session identities, approval boundaries, and truthful cancellation. Interrupted work is never automatically replayed. Use Amplifier Converge whenever naming that application. Keep credentials, transcripts, user settings, and private validation artifacts outside Git. Record tested revisions and distinguish fixture evidence from live model tests. Do not change provider protocol…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read docs/VISION.md and docs/contracts.md, then the exact local interface needed for the next outcome. Shared promises live in the Constellation boundary and shared agreements; link them rather than copying them into local guidance. Use Converge for ownership, changes and verification. Keep local agreements focused on this component's contribution. Exact APIs, schemas and tests remain authoritative in their technical homes. Current…
VISION.md is the entry point for what this project is converging toward. The skills under skills/ are the implementation. For local development, use your agent's tools to load or read skills from skills/. The project has one word for the thing it works on: a risky assumption. Use it, and the terms below, in skill text, script output, UI copy, and when reporting to the user. Introducing a synonym costs the reader a translation step every time they meet it,…
MicrosoftAGENTS.md