Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
Clarify authorized GitHub identities for contributors
picodot3e2f6b2899ad
diff --git a/AGENTS.md b/AGENTS.mdindex 7570f890a8..eac481a3f1 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -9,7 +9,7 @@ Guidance for every AI coding agent working in this repository — Claude Code, CEvery agent must leave discovered problems either fixed and verified or captured in the owning project's issue tracker before finishing. This includes product bugs, broken expectations or assumptions, workflow/process defects, flaky tests, and concrete inefficiencies encountered during the task. “Pre-existing,” “unrelated,” and “out of scope” are reasons to file a follow-up, not reasons to lose the finding. Stay alert while doing the requested work; this does not require an unrelated full-repository audit.- **Fix now when bounded and safe; otherwise file.** Preserve the requested scope and unrelated work. Do not weaken assertions, skip tests, or retry until green to hide a failure. If the expectation is wrong, correct the contract and its test together.-- **Route to the owner.** Shared slashdo command, renderer, or workflow defects belong in [atomantic/slashdo](https://github.com/atomantic/slashdo/issues); PortOS behavior, integration, configuration, and repository instructions belong in this repository's tracker. Use the configured repository remote for forks or managed apps. Cross-link issues only when both projects need changes. Use only the `atomantic` GitHub account for repositories owned by `atomantic`.+- **Route to the owner.** Shared slashdo command, renderer, or workflow defects belong in [atomantic/slashdo](https://github.com/atomantic/slashdo/issues); PortOS behavior, integration, configuration, and repository instructions belong in this repository's tracker. Use the configured repository remote for forks or managed apps. Cross-link issues only when both projects need changes. Contributors must use their own authorized GitHub identity, not impersonate the repository owner. Work delegated by Pico uses `picodot`; the owner’s local agents may use `atomantic` when authorized.- **Search before filing.** Reuse an existing issue that covers the finding; add new evidence when useful. For a new issue, include redacted evidence or reproduction steps, expected versus actual behavior, affected files, a chosen next step, and acceptance criteria. Distinguish a suspected flake from a reproduced cause. Follow the owning project's issue conventions; for PortOS, read [portos-file-issue](.claude/skills/portos-file-issue/SKILL.md) and the canonical label guidance in `server/lib/dispatchLabels.js`.- **Close the loop.** Report fixes and issue links in the handoff. Chat-only notes and TODO comments do not replace a filed issue. If tracker access fails, report the exact blocker and provide a ready-to-file issue body; never claim it was filed.