Mythos

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 — needleMode supports auto, always, and never for one memo title.
  • Tag-wide exclusions — needleTagExclusions mutes 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, the editor's suggestion card lists every memo claiming it so you can choose.

Getting Started

  1. Open Settings → Enrichment.
  2. Under Customize enrichments, choose how strictly your AI's writes are checked (Off, Suggest, or Require) before turning Require on.
  3. Search for a memo under Customize enrichments and set it to Never enrich for noisy ordinary-word titles or Always enrich for distinctive product and entity names; mute whole tags in the same section.
  4. Use PATCH /api/me/{username}/{id}/enrichment to set one memo's needleMode.
  5. Use PATCH /api/settings/link-lint to set library-level needleTagExclusions.

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 auto do? auto enforces the title unless it carries a muted tag or is a placeholder such as Untitled; always forces enforcement, and never mutes 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

Contexts

Created with 💜 by One Inc | Copyright 2026