← ClaudeAtlas

enact-work-coordinationlisted

Live Enact Work with authenticated tools: propose, claim, run, evidence, effects, defer/wake.
SylphxAI/skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill SylphxAI/skills
# Enact Work Coordination Use Enact as live **work coordination** authority without turning it into the owner of source, provider, or static instruction facts. Read [references/enact-adapter-contract.md](references/enact-adapter-contract.md) for current semantic tools, REST mappings, provider observations, and source locators. Resolve exact fields from the live MCP schema or versioned product API. ## Product identity (ADR-0045) ```text Organization └── Project ├── Work / Claim / Attempt / Run ├── Decisions / Incidents / Knowledge └── Optional external resources (Git, CI, services, …) ``` - **Organization** is the commercial boundary (membership, billing, isolation). - **Project** is the durable work unit. A Project may have zero, one, or many repositories. - **Repository ≠ Project.** Never invent Organization/Project from a repo name. - **GitHub / GitLab / forges are optional connectors.** Enact Work Graph must run without any forge. Connector loss yields stale observations, not a dead work ledger. - Residual `tenant_id` / `workspace_id` keys may appear on cutover APIs only; do not teach them as product vocabulary. ## Operating method 0. **Availability gate (OAuth-first).** Enact is in-scope when the MCP client can reach `https://enact.sylphx.com/api/mcp` and list tools after OAuth against protected-resource metadata (`/.well-known/oauth-protected-resource`). Verify `work.propose_or_get` (or equivalent) is in the live tool list. If tools