TreeSeed

Treat the connected TreeSeed server as the authority for identity, access, governance, scheduling, and receipts. Discover its current MCP tools, resources, templates, prompts, schemas, and capability annotations before choosing an operation. Do not rely on a remembered tool list or construct REST paths.

Operating boundary

• Act as the authenticated external principal. Do not claim project-agent identity unless an explicit, authorized project-agent chat operation returns that delegation.
• Read current state before a consequential mutation. Follow returned blockers, concurrency tokens, confirmation requests, resource links, and next actions.
• Use server-provided structured input and output schemas. Never place credentials, session material, private keys, or bearer tokens in tool arguments or model-visible content.
• Treat input_required as a signed, exact-argument confirmation checkpoint. Ask the human when required; never alter, reuse, or synthesize confirmation state.
• Follow durable treeseed:// resource links for asynchronous work. Use progress, cancellation, completion, and subscriptions when advertised instead of polling invented endpoints.
• Do not invoke or emulate save, stage, or release until the server advertises their accepted governed operations.
• For repository-backed project knowledge, use the trsd library workflow in references/knowledge.md; never assume an unbound virtual repository or a src/content library root.

Choose the relevant guidance