Build a contextual knowledge collection · 3 / 5

Add personal context for the operator

Keep general guidance and add a separate note for the user who contributes it.

YOUR TASK

Make this happen

3 steps

Add knowledge_note "my_shift" with the supplied morning-shift advice and PERSONAL scope.
Attach it to concept.roller.id; keep it PENDING with CHAT_DISTILLED provenance.
Preserve the original TENANT note unchanged.

THE IDEA BEHIND IT

Who owns the personal note?

Imagine Alice contributes this note while signed in. The server sets authorUserId from that authenticated user; it is computed, not an IaC field. Creating a service_account or setting a user ID here would not impersonate Alice. This browser exercise has no authenticated author and creates no notes.

Personal context is not destructive replacement

Once LIVE, Alice alone can retrieve her PERSONAL note. It receives a 1.5× personal ranking multiplier; other users still get tenant guidance. Relevance, graph distance and trust also affect ordering, so this is contextual preference, not a guaranteed override. The general note remains intact.

When advice disagrees

Keep the general guidance available and explain the personal qualification. Actual retirement uses the supersededBy update API and is a different lifecycle operation; do not retire tenant guidance just to express one operator’s preference.

The real CLI validates declarations and expands CSV locally. Authentication, graph bindings, note confirmation, ranking and retrieval are explained, not simulated. No resources are created.

What you’re building: Help an operator find general guidance, their own qualifications and advice specific to the press they are using.

This step starts with the earlier solution and one new challenge. Each lesson keeps its own draft.

Read the starter files

concept.cococo

concept "roller" {
  label = "Roller Jamming"
  conceptKind = "failure-mode"
}

main.cococo

knowledge_note "setup" {
  kind = "CONCEPT"
  body = "In high humidity, warm the shop before a long run to reduce roller jams."
  scope = "TENANT"
  status = "PENDING"
  provenance = "CHAT_DISTILLED"
  conceptId = concept.roller.id
}

personal.cococo

knowledge_note "my_shift" {
  kind = "CONCEPT"
  # Supplied body: "For my morning shift, ask the shift lead to check humidity before warming the shop."
  # TODO: assign body using the value above.
  # TODO: add scope — see the task above.
  # TODO: add status — see the task above.
  # TODO: add provenance — see the task above.
  # TODO: add conceptId — see the task above.
}

Reference: knowledge · authoring