You are the maintainer of this personal wiki. The wiki is a persistent, interlinked knowledge base built from raw source documents. You read sources, extract knowledge, and integrate it into evolving wiki pages. The user curates sources, directs analysis, and asks questions; you handle the bookkeeping. The wiki root folder is: {{localFolders.wiki-root.path}} The wiki's default operating schema is: {{localFolders.wiki-root.agentsPath}} Before ingest, query, lint, index, or maintenance work, read that wiki-root AGENTS.md file. It is the source of truth for page…
You are the maintainer of this personal wiki. The wiki is a persistent, interlinked knowledge base built from raw source documents. You read sources, extract knowledge, and integrate it into evolving wiki pages. The user curates sources, directs analysis, and asks questions; you handle the bookkeeping. The underlying pattern is described in IDEA.md (Karpathy's "LLM Wiki" gist). Read it if you need the philosophy; this file is the operational schema. The subdirectories under wiki/ are conventional, not enforced. Add new…
You are the CEO. Your job is to lead the company, not to do individual contributor work. You own strategy, prioritization, and cross-functional coordination. Your personal files (life, memory, knowledge) live alongside these instructions. Other agents may have their own folders and you may update them when necessary. Company-wide artifacts (plans, shared docs) live in the project root, outside your personal directory. You MUST delegate work rather than doing it yourself. When a task is assigned to you: You MUST…
About this repo: repo-weaver is a deterministic git → wiki front-end over the wiki-weaver engine. It makes zero direct LLM calls; all synthesis/query is delegated to wiki-weaver via subprocess. See ARCHITECTURE.md for the full picture. This file is auto-loaded each session. Treat it as binding repo convention. Whenever a change touches any of: you MUST, in the same change: A change that alters architecture without updating these is incomplete. Consult these conventions at the start of work and at 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/, notes/CONVERGE.md, notes/PLAN.md, notes/ENGINE-BOUNDARY.md and SMOKE_TESTS.md before changing behavior. Keep runtime imports in host/composition and their app-policy adapters; widgets consume identified events only. Independent modules may import kernel contracts, but never the host package or widgets. Prefer independent host/module replacements; honor each upstream repo's rules if a demonstrated seam fix is needed. Never put UI policy in the…
The default backend is the Docker Compose Smart Tool digital-twin-universe, not the legacy Incus CLI. Preserve the root namespace anchor, stable agent names, historical evidence and explicit unsupported-binding response for old instances. Run python -m pytest tests/ -q; the opt-in deterministic lifecycle is tests/run_smart_dtu_lifecycle.py (requires an explicitly selected Docker endpoint, private state root and operation ID). Never run it against live user state. @README.md @bundle.md @agents/setup-digital-twin.md @agents/validator.md @context/amplifier-ecosystem-map.md
Vision-first, contract-driven (Converge). docs/VISION.md governs the contracts; the contracts govern the code. A change that contradicts a contract lands in the contract first (proposal → owner's word), then in code. 1. Simplicity is the requirement, not a style. Before adding a mechanism, name the cost that was actually paid without it. The predecessor shipped a resident server, an evidence ladder, tombstones, fingerprints, semantic clustering, a pending pool, ceilings, and a 63-row ledger — and an empty store. The bar for…
This repo is a bundle with three layers: a zero-dependency library at the root, a thin hook adapter under modules/, and the behavior that wires them together. Keep these layers separate — that separation is the entire point of this repo's shape. Do not collapse these back into a nested modules/redaction/ layout. The library moved to the repo root deliberately (see amplifier-module-hooks-redaction for the "before" shape this replaced) so that a consumer can import redaction out-of-process without going through Amplifier…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Use Amplifier Converge as the collaboration method. Read docs/VISION.md and the contracts for the next outcome. Derive the gap by inspecting current source, capabilities and relevant behavior; do not maintain a parallel umbrella status or gap inventory. docs/working-together.md explains the local practice. Do not load every contract or historical conversation by default. - Use family.toml to find the Microsoft component…
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. This repository develops the Amplifier Converge methodology. Start with README.md, docs/VISION.md, and the applicable contracts. For work applying the method elsewhere, use guides/agent-guide.md; for a guidance review, use guides/reviewer-guide.md. Keep the shared promises portable across people and agent systems. Put practical application in the guides, with links to the governing contracts. Keep the methodology independent of a particular runtime, database,…
A temporary working repository for cross-repo development. Created fresh for a task; destroyed when complete. Invariant: Every repo in this workspace lives as a subdirectory of cwd with its own .git — either a submodule (remote exists) or a local-only git repo (pre-publish). The workspace root is never the root of any project's source tree. Forbidden — no matter how convenient it seems: Why: The workspace is destroyed at session end. Self-containment is what makes destruction safe. Edits outside cwd,…
Guidance for coding agents working in this repository. Read this file first, then the nested AGENTS.md closest to the files you are changing — it takes precedence for its folder. VS Code users: nested AGENTS.md files are only loaded when chat.useNestedAgentsMdFiles is enabled in settings. Without it, open the nested file listed in the repository map yourself before working in that folder. A reusable runtime for long-running, auditable, agentic business processes on Power Platform and Copilot Studio (GitHub Copilot harness),…
Playbook for adding a new business process (claims, loans, onboarding, …) on top of BusinessProcessCore. Read core/AGENTS.md first for the tables, choice values, step trigger contract, and human task contract. Use order-processing/ as the template to copy — every recipe below points at the order-processing component that implements it. Ground rules: a process is its own solution layered on the installed core; it contributes workflows, agents, review widgets, security roles, and environment variables, and does not modify the core (except…
Purchase orders arrive by email, agents extract and validate them, two human gates approve, and a final agent emits an SAP-ready payload. Business-level description: README.md. Generic patterns: business-processes/AGENTS.md. Use this file to customize Order Processing or to find the exact component to copy for a new process. Data keys: extracted-order, extracted-order-review.{decision,notes,edited_order}, order-evaluation.result, order-evaluation-review.{decision,notes}.
Read this before building or changing a business process. It catalogs what the core gives you and the contracts a process must honor. The authoritative sources are spec/business-process-data-model-spec.md and the Business Process API contract; if this file disagrees with them, they win — and fix this file. The core ships no workflows. Every workflow, notification, and task-raising action lives in the business process solutions. Rules from the spec that every process flow must follow: - After every faf001_bpstep write, update…
React 19 + TypeScript + Vite + Tailwind CSS 4 + TanStack Query, hosted as a Power Apps code app. It gives users their task queue, the review widget for each task, and the timeline, attachments, artifacts, and outputs of every process instance. Full developer guide: README.md. The console is part of the core and shared by every business process. The usual reason a process touches it is to add a review widget. npm test reads ../../plugins/business-process-api/spec/ — keep the…
C# plug-in that implements the faf001_* Custom Actions behind the Workflow Console and the monitoring agent. The public contract is README.md; the build, test, and registration procedure is DEVELOPMENT.md. Read both before changing behavior. A business process should almost never need to change this project. Process flows write the core tables directly through the Dataverse connector. Change the API only for process-agnostic capability the user has agreed to add to the core. - Target framework net462 (Dataverse sandbox) — no…
Remember the law of diminishing returns to decide if something should fit or not here. Before drafting, editing, or returning repository prose, invoke /humanize-writing. This includes technical documentation, session kits, runbooks, Markdown, slide content, and user-facing explanations. In this repository, use the skill to simplify wording and remove AI-patterns from technical content. Its general technical-writing exclusion does not apply here. Use the clear-thinker voice unless the user requests another voice. Before finishing, complete both checks: 1. Apply the prose simplification…
MicrosoftAGENTS.md