Knowledge seeding

Use this workflow when you want to load a first batch of Eden guidance without typing every note into Knowledge mode manually.

Recommended flow

1. Shortlist the first candidate topics in content/eden/knowledge-candidates.md.
2. Copy the selected items into content/eden/knowledge-import.template.csv.
3. Run a dry run of the import.
4. Import the rows as drafts.
5. Test Eden with the prompts in content/eden/operator-question-pack.md.
6. Approve the knowledge items you are happy with.

CSV columns

Required:

• title
• guidance

Optional:

• when_to_apply
• recommended_answer
• source
• evidence_note
• confidence
• status

Notes:

• Keep each field on a single line.
• Quote fields that contain commas.
• If status is blank, the import task uses the task default.
• Approved imports require an explicit confirmation flag.

Import command

Dry run:

deno task knowledge:import -- \
  --file content/eden/knowledge-import.template.csv \
  --customer-id <customer_uuid> \
  --user-id <user_uuid> \
  --dry-run

Draft import:

deno task knowledge:import -- \
  --file content/eden/knowledge-import.template.csv \
  --customer-id <customer_uuid> \
  --user-id <user_uuid>

Approved import:

deno task knowledge:import -- \
  --file content/eden/knowledge-import.template.csv \
  --customer-id <customer_uuid> \
  --user-id <user_uuid> \
  --status approved \
  --allow-approved

Guardrails

• The task skips non-archived items with the same title + source for the same customer.
• Draft import is the default.
• Approved import is blocked unless --allow-approved is supplied.
• The task creates the same intelligence_knowledge_item records used by Knowledge mode and Assistant mode retrieval.

Test pack

Use content/eden/operator-question-pack.md after import to check:

• whether Eden finds the new guidance,
• whether answers sound operationally correct,
• where extra policy notes are still missing.