What problem does it solve? Authoring semantic relationships in a Bindle context graph requires strict endpoint legality, canonical candidate keys, and human-confirmed acceptance; doing this by hand risks invalid edges, fabricated keys, or silent repairs that corrupt the graph. ## Core Features & Use Cases - Proposal drafting: Builds proposal.json envelopes with source, relationship, target, basis, and explanation, grounded in real node IDs from the CLI's preview output. - CLI-driven validation: Runs propose, confirm, and apply so the deterministic CLI remains the sole authority for endpoint legality, candidate keys, and acceptance. - Ontology safety: Refuses reserved relationships like implements, normalizes symmetric contradicts to one canonical candidate, and surfaces the CLI's exact rejection findings instead of silently repairing invalid proposals. - Use Case: While reviewing a design decision, you ask the agent to record that a decision constrains an assumption; the skill inspects the graph, drafts the proposal, validates it via propose, and presents the candidate for your explicit confirmation. ## Quick Start Ask the agent to propose a semantic relationship between two nodes in your Bindle context graph and confirm the validated candidate it returns.
