knowledge-entities

Resolve and enrich entities

Find who or what an entity is before asking, decide whether it deserves a page, then write a sourced profile and link it both ways. Read a reference only when its step needs it. Shared references are identical across Knowledge skills; if another Knowledge skill brought you here, don't reread ones you already read.

• setup: always, first (status, ontology, search)
• identity: resolving an entity; whether to create a page
• enrichment: tiers, what to extract, external lookups, bulk runs
• profiles: page structure, creating or updating
• writing: before writing page prose
• sources: retaining sources and citing them
• assertions: claims and relationships about the entity
• publish: page writes and batches
• recovery: any uncertain, rejected or conflicting write
• verify: verification and report
• evidence repair: only for an authorized evidence-set repair

Contract

• Check Knowledge before asking the user or searching externally. Ask only with a hypothesis.
• No stubs or placeholders: every page's first line says who or what it is.
• Every fact has an inline citation; every enriched page links to its source and the source links back.
• Scale effort to importance. When in doubt, don't create a page.
• Never overwrite user-written assessments; flag contradictions with both citations.

Steps

1. Identify entities

List the people, companies, projects and concepts in the source. Separate actual participants from third parties mentioned in passing.

Done when: each entity is marked participant, substantive or incidental.

2. Resolve each one

Run the resolve chain in identity. Reuse an existing page's ID. Decide create, update or skip using its page-creation rules, and pick the best-fitting declared ontology type.

Done when: each entity has an existing ID, a create decision with a type, or is skipped; ambiguous identities are recorded as partial or unresolved.

3. Gather signal

Extract texture from the source and, for Key and Notable entities, look up what's missing (enrichment). Only supported claims move on; inferences stay labeled where they appear.

Done when: each entity has its supported facts and texture, each with a citation, or a reason it has none.

4. Write

• Create: introduction, State and the first Timeline line, plus only the optional sections the evidence supports (profiles).
• Update: add the Timeline line; edit a State topic only when its meaning changed; use knowledge_edit_body for local edits.
• Use declared ontology fields only; omit unknown values.
• Create claims and evidenced relationships for independently useful assertions (assertions). Markdown links don't create relationships.

Done when: every planned write has a published receipt.

5. Cross-reference

Link source → entity and entity → source using observed paths. Update related pages when the new signal matters to them: the company page from a person, and the reverse; the parent project from a sub-feature.

Done when: both link directions exist for every linked entity.

6. Verify

Run verify with planned expectedLinks in both directions, associations and relationship endpoints. Reread each changed page against writing and the no-placeholder rule.

Done when: structural checks pass and every changed page reads as a real briefing.

Report

Return resolved IDs, created/updated/reused pages, sources used, unresolved or partial identities, contradictions and skipped work to the caller or user.