distribute

Promote all processed notes to their final locations as permanent pages.

Sources to scan (both):

• inbox/ready/ — all .md files
• thinking/ — .md files with status: ready only (exclude thinking/archive/ and thinking/README.md)

For each .md file found in the above sources:

1a. Route thinking notes — If a file in inbox/ready/ has status: thinking, move it to thinking/[YYYY-MM-DD]-[name].md and skip it from distribution.

1. Read frontmatter — Extract domain, type, name, and project fields.

2. Validate domain exists — Check that domains/[domain]/ exists. If domain is missing or domain: work (cross-domain), route to work/04_PAGES/ instead. If domain does not exist and is not "work", ask user to create it first.

   Use the user context loaded at session start (from USER.md) to determine whether ambiguous content is work-related vs domain-specific. If content is professional/work-related and no domain clearly fits, offer work/04_PAGES/ as the default.

3. Determine destination:

   • Default: domains/[domain]/02_PAGES/ (or work/04_PAGES/ for cross-domain content)
   • If type is belief, frame, lesson, model, or goal and the domain has relevant memory files: offer to append to existing memory file instead of creating a new page
   • If project field is set: link from the project file after placement
   • If type: 1-1: route to work/02_1-1/ using the per-person accumulating pattern — see step 3a below.
   • For domain pages: apply steps 3b and 3c to assign a navigation type and sub-folder route.

   3b. Assign navigation type from content analysis

   If the note is routing to a domain (not work/), assign one of the six navigation type values by content analysis:

   Signals	type
   "we decided", rationale, trade-offs, outcome	decision
   reference material, external source, processed URL	source
   idea, framework, mental model, definition	concept
   AI brief, synthesis, session output, generated report	output
   filed question, answered query, Q&A	question
   audit, analysis, health check, status report	report

   If the note already has a valid navigation type set by /process, use it (the AI may refine it if the content analysis strongly suggests otherwise). Non-navigation types (goal | plan | research | idea | meeting) pass through unchanged and land flat in 02_PAGES/.

   3c. Route to typed sub-folder (if exists)

   Map the assigned type to its plural folder name:

   type	Sub-folder
   concept	concepts/
   source	sources/
   decision	decisions/
   output	outputs/
   question	questions/
   report	reports/

   • If domains/[domain]/02_PAGES/{type_plural}/ exists → route there.
   • If it does not exist → land flat in domains/[domain]/02_PAGES/ (sub-folder emerges later via /audit cluster detection).
   • Non-navigation types always land flat in 02_PAGES/.

   3a. 1:1 routing (accumulating file pattern)

   1-1 notes do NOT create a new file per meeting. Instead:

   a. Extract person field from frontmatter (e.g., "Babis Pagonis"). b. Check if work/02_1-1/[Person].md already exists. c. If the file exists — absorb mode:

   • Extract the meeting date and topic from the note content
   • Prepend a new ### [date] — [topic] section immediately after ## Meetings heading
   • Update ## Latest Summary with the new meeting context
   • Update the date frontmatter field to the new meeting date
   • Update description frontmatter with a fresh ~150-char rolling summary
   • Mark source note status: processed
   • Archive source to brain/MASTER_ARCHIVE/ and log to brain/INGEST_LOG.md with destination [[work/02_1-1/[Person]|[Person]]] ([date] section)
   • Skip the file-move steps (file already exists at destination) d. If the file does not exist — create mode:
   • Create work/02_1-1/[Person].md using the 1:1 Note schema from ASSET-CLASSES.md
   • Structure: ## Latest Summary + ## Meetings with the first ### [date] — [topic] section + ## Related with PEOPLE.md wikilink
   • Proceed with normal archive + log steps