validate
Graph Integrity Gate - Ensure nodes and relations can exist in the causal graph.
What this skill does
# Graph Integrity Gate This skill determines whether a node and its local causal subgraph can exist. Validation does not evaluate quality or design semantics. It verifies structural conditions required for causal traversal. > [!IMPORTANT] A node is valid only if its presence does not create a logical contradiction in the graph. Cosmetic or > stylistic issues must NOT cause failure. --- ## Core Principle Validation checks **existence**, not interpretation. - If validation fails → the graph contains a structural contradiction - If validation passes → reasoning may safely operate Validation rejects impossible structures, not incomplete ones. Validation guarantees the graph is a possible world, not a complete world. --- ## 0. Schema Topology Understanding Before running validation, the agent MUST read `docgraph.toml` to establish the allowed structural topology. `docgraph.toml` is the sole normative source. If unread, the agent MUST stop. The agent MUST extract: - Allowed node types and their identifiers - Allowed relation types (`r.type`) and their directionality - Allowed target types for each relation - Required and forbidden relation rules All validation decisions MUST be justified against this topology. --- ## 1. Automated Structural Checks Run automatic checks before manual inspection. ```bash docgraph check ``` If this fails → **FAIL immediately** --- ## 2. Schema Integrity All nodes and relations must conform to `docgraph.toml`. Failure cases: - Undefined node type - Undefined relation type - Disallowed relation direction Result: FAIL --- ## 3. Referential Integrity All references must resolve. - inbound references resolve - outbound references resolve Dangling references → FAIL --- ## 4. Identity Uniqueness Node identifiers must be globally unique. Duplicate ID → FAIL --- ## 5. Causal Contradictions The local graph must not contain logical contradictions that prevent traversal. A structure is invalid only if realization is impossible, not merely incomplete. Examples: - constraints block all realizations - cyclic dependencies preventing resolution - mutually exclusive requirements - relation semantics conflict - schema makes realization unreachable Any detected → FAIL --- ## Minimal Tooling ### `docgraph check` ```bash docgraph check ``` ### `docgraph describe` (optional) Use only when confirming unresolved references around a specific node. ```bash docgraph describe <ID> ``` --- ## What Validation Does NOT Check The following MUST NOT cause failure: - naming elegance - directory placement - template formatting - SRP granularity - documentation completeness These belong to alignment or hygiene review. --- ## Validation Report ### Target - **Node**: [ID] ### Structural Results | Check | Result | Notes | | :-------------------- | :-------- | :---- | | Schema topology | READ | | | Schema integrity | PASS/FAIL | | | Referential integrity | PASS/FAIL | | | Identity uniqueness | PASS/FAIL | | | Causal contradictions | PASS/FAIL | | --- ## Final Decision **PASS** → Node may exist in the graph **FAIL** → Graph integrity would be broken **FINAL DECISION: [PASS/FAIL]**
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.