Build a contextual knowledge collection · 4 / 5

Add context for one press

Give Press A its own caveat while retaining both general and personal knowledge.

YOUR TASK

Make this happen

3 steps

Add knowledge_note "press_a" with kind = "ENTITY" and the supplied Press A TypeID.
Use the supplied red-roller advice with TENANT, PENDING and CHAT_DISTILLED.
Keep the concept and both previous notes; omit conceptId on this entity note.

THE IDEA BEHIND IT

Target and audience are separate

An ENTITY note describes one resource; TENANT/PERSONAL still controls who can see it. A note has exactly one target. entityId is a TypeID whose prefix identifies the resource kind; entityType is computed. The supplied Press A ID is an exercise fixture, not a real machine.

Layer context in a real retrieval

A real Press A seed reaches its direct entity notes. To also reach Roller Jamming concept advice, bind that existing press to the concept with an instance_of edge using captureKnowledge. Those edges and retrieval run on the platform; this exercise validates declarations without inventing edge resources.

Review all layers

After confirmation, an operator can see general guidance plus the press caveat; Alice can additionally see her personal note. Pending notes remain excluded in every layer. Specificity supplies context, not an unconditional winner.

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"
  body = "For my morning shift, ask the shift lead to check humidity before warming the shop."
  scope = "PERSONAL"
  status = "PENDING"
  provenance = "CHAT_DISTILLED"
  conceptId = concept.roller.id
}

press.cococo

knowledge_note "press_a" {
  kind = "ENTITY"
  # Supplied body: "On Press A, ask the shift lead to inspect the red roller before the first long run."
  # 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.
  # Supplied entityId: "wcr_01k00000000000000000000001"
  # TODO: assign entityId using the value above.
}

Reference: knowledge · authoring