Needle Controls in 📝MythOS are 📝Enrichment settings that decide which memo titles act as required link targets for agents. They give library owners a curated dictionary for link lint: a title can stay automatic, always act as a needle, or never act as one, and whole tag groups can be excluded from enforcement. They exist because common words like work or time can be real memo titles without every ordinary sentence referring to them. Needle Controls are for creators using MCP, the Internal Agent API, or AI drafting workflows who want agent writes to strengthen the graph without drowning in junk link violations.
Key Capabilities
- Per-memo mode —
needleModesupportsauto,always, andneverfor one memo title. - Tag-wide exclusions —
needleTagExclusionsmutes every memo carrying a configured tag. - Owner-only writes — only the real library owner can change enforcement policy.
- Agent-safe payloads — muted needles do not block writes or appear in agent-facing lint output.
- Manual common-word policy — owner curation replaces automatic stop-word muting.
- Title conflicts — a title two memos share enforces for neither, and the owner can list every conflict from the needle settings surface.
Getting Started
- Open Settings → Enrichment.
- Review which names your agents are asked to link before turning Require mode on.
- Mark noisy ordinary-word titles as not required, or force distinctive product and entity names to required.
- Use
PATCH /api/me/{username}/{id}/enrichmentto set one memo'sneedleMode. - Use
PATCH /api/settings/link-lintto set library-levelneedleTagExclusions.
FAQ
- What is a needle? A needle is a memo title or alias that Enrichment recognizes in prose and can ask an agent to link.
- What does
autodo?autolets MythOS decide from the title safety rules;alwaysforces enforcement, andnevermutes that title. - Why not mute common words automatically? Automatic common-word muting was built and deliberately removed because owners know when an ordinary word is actually a company, product, or personal concept.
- Can collaborators change needle policy? No. Aliases and descriptions can be grant-writable, but enforcement policy is owner-only because muting or forcing needles changes the owner's corpus gate.
- What happens when two memos share a title? That title stops acting as a needle for both, so nothing is linked automatically and no agent is asked to link the wrong one. The editor's suggestion card lists the memos claiming it and you pick. Resolve it by renaming one, or by marking one
never. - Do muted needles still reach agents? No. Muted needles stay out of agent-facing lint payloads and context sections, while human editor suggestions remain advisory.
Related
- 📝Mentions & Backlinks — the graph connections that linked needles protect
- 📝MythOS MCP — the agent surface where Require mode most often matters
- 📝Internal Agent API — the REST surface for non-MCP agent writes
