Skip to content

feat(client-vue): Knowledge-Studio workbench screen + Reasoning Chain Inspector integration (KE-1 UI) #112

Description

@mdheller

Follow-up UI surface for the KE/Dictionary workbench contract shipped in #111 (tools/knowledge-engineering/, KE-1). The contract + teeth landed; this issue tracks the Knowledge-Studio-equivalent screen and the platform-screen integrations. Consume-not-fork; wire into existing surfaces, don't rebuild.

Surface (client-vue — canonical web shell)

Home: ~/dev/socioprophet/socioprophet-web/client-vue. Add the WKS-equivalent screen rendering the KnowledgeEngineeringWorkspace loop:

documentSet → annotate → Entity Types → Relation Types → Dictionaries → Rules → Versions → (rule-based + ML model)

  • Entity/Relation Types panels — read-only bindings into the governed registries (regis entity-class Add OrgGov control-room workspace fixture #16, semantic-role-kind integ: land 1 clean backlog branches #22, ontogenesis OWL/SHACL). Surface must show the warrant (which registry + member), never let a free-typed type in.
  • Dictionaries panel — governed Systema Concept Entries (ontogenesis Platform/Systema): source-anchor, promotion-state lifecycle, revision history, provenance class chip (learned | human_authored | imported). No free-text "add word to list" — a static-match affordance must be impossible by construction (mirrors KE-T1).
  • Authoring — the user as first-class author: add/overwrite/annotate/define as governed AuthorshipEvents; overwrite = supersede prior (retained), each author-attributed + receipted. Show the supersession history and the active (max) version.
  • Rules / Versions — rule editor over governed types only; version snapshots each showing their receipt.

Reasoning Chain Inspector integration (coordinate — being ported to Vue concurrently)

Expose the reasoning-chain annotations (regis SemanticTokenTree token roles) as KE input: from an inspected chain, promote a token role → candidate entity/relation/dictionary term → governed, receipted promotion (the spec.annotations[].promotedTo + promotionReceiptRef path). The Inspector and the KE workbench should share the annotation selection model.

Related platform-screen integrations (pw#76 dashboards)

  • Schema explorer (pw#76 item 9) — reuse for the entity/relation-type registry view.
  • Knowledge Hub / annotation overlay + ZOIN workspace (pw#76 item 10 / pw#103) — the annotation overlay is the document-annotation surface feeding this loop; wire to the graphrag-grounding annotation→KG path.
  • Cockpit view — a KE-freshness / promotion-receipt view alongside the existing receipts/policy cockpit.

Runtime wiring (epic #33)

Resolve registryRef.member against the LIVE regis + ontogenesis SHACL/OWL gates (contract pins the enums; CI re-syncs); route promotion/authorship receipts through the shared Ledger.Push triRPC verb; mint the Systema-side urn:srcos:receipt: for concept promotions.

Contract + teeth: #111. Cross-ref pw#76 (items 9/10), pw#103, regis #16/#22/#27, ontogenesis Systema.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions