ai.geodesiclabs/governance-platform · v1.2.0 · agents-and-memory
ai.geodesiclabs/governance-platform is healthy: it completed an MCP handshake in 1192 ms and exposes 37 tools.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Endpoint: https://app.geodesiclabs.ai/mcp (streamable-http)
No repository listed · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 37 |
| Latency | 1192 ms |
| Last checked (UTC) | 2026-10-15T15:25:12.927Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T15:25:12.927Z | Healthy | 1192 | |
| 2026-10-14T09:00:19.001Z | Healthy | 2669 |
validate | Validate structured data against a Blueprint's rules BEFORE the result is used. Returns PASS, FAIL, or REVIEW with plain-language findings, repair suggestions, a determinism hash, and a re-verifiable certificate. Same input + same rules = same verdict, every time. |
validate_repair | Validate structured data against a Blueprint and, when it fails, include repair suggestions (corrected values with the rule each fix is based on) in the same call. Same verdicts as validate: PASS, FAIL, or REVIEW, with reasons and proof. |
create_blueprint | Create a Blueprint - the governance contract validation runs against. A Blueprint defines what correct means for your data: fields, the math that must hold between them, and acceptable ranges. Start from load_rule_pack or discover_patterns if you have no rules yet; invoke the bluepr |
list_blueprints | List the Blueprints on this account with field/rule/constraint counts and mode. Use the returned workflow_name as 'blueprint' in validate. |
repair | One-shot repair: return corrected values that would make failing data valid under the Blueprint. Use repair_path to see the steps instead. |
check_blueprint_health | Static pre-deploy analysis of a Blueprint's rule set. Returns a health verdict - healthy, acceptable, fragile, rigid, split, brittle_islands, or unsatisfiable - with advice, including joint conflicts pairwise checks miss. |
compare_semantic_equivalence | Compare two payloads under the dual-hash design: content_hash is content_hash normalizes field order and numeric formatting. Semantic comparison preserves field roles; renaming requires an explicit bijection. With supplied rules, scalar types and whitespace remain significant. Struct |
govern_inference | Quality-govern an in-progress AI generation step BEFORE its output is used (complements validate, which checks finished documents). Returns an action - STOP, CONTINUE, REPAIR_REGION, REUSE_MOTIF, REVIEW, ESCALATE - with a plain-language explanation. Structural scores do not establish |
get_inference_trace | Retrieve the durable audit trail for a governed generation: every recorded decision and its reasons. |
recent_inference_decisions | Recent generation-governance decisions in this owner's Blueprint version. |
verify_certificate | Independently re-verify a validation certificate. Integrity mode checks the hash chain; full mode (certificate + original data) recomputes every attested rule from scratch - trust nothing, recheck everything. |
profile_blueprint_robustness | Sweep the Blueprint's numeric constraint bounds and report verdict stability: the stable band, the scales where the verdict first flips, and advice. Use before deploying bound changes. |
forecast | Deterministic forward reasoning: from the current data state, generate and rank the valid next states reachable under the Blueprint's rules. |
discover_patterns | Learn candidate validation rules and structural document types from a batch of your records, deterministically - no Blueprint required. Promote results with approve_rule. Source data is not stored. |
repair_path | Find the shortest sequence of field changes taking invalid data to a valid state, as an ordered path of intermediate states. Different from repair (one-shot nearest fix): use repair_path to explain or audit the fix, or compare alternative repairs. |
counterfactual | Run the same data under two rule sets and compare which future states remain valid - what-if analysis for rule changes. |
analyze_anomaly | Explain whether a record fits the usual pattern for records like it, and which fields stand out. No Blueprint required. |
create_chain | Create a multi-agent sequential chain: stages validate in order against one Blueprint, repairs propagate forward, TTL bounds the run. Siblings: submit_chain_stage advances the chain; handoff_audit verifies a transition between stages. Returns chain_id. |
submit_chain_stage | Submit data for the chain's current stage; the platform validates it and advances the chain if it passes. Response includes next-stage info and accumulated repairs. |
handoff_audit | Audit a handoff between two chain stages: a context capsule of verified facts from the prior stage, and (if proposed_data is given) a compatibility verdict that catches fields mutated in transit. Siblings: create_chain, submit_chain_stage. |
approve_rule | Promote a rule discovered by discover_patterns into Blueprint-ready form. |
reject_rule | Reject a discovered candidate rule so it will not be promoted into a Blueprint. Pair with approve_rule after discover_patterns. |
structural_types | Retrieve the document categories a discover_patterns session identified (counts, distinguishing fields, domain hints). Read-only; returns status=no_session if discovery has not run for this namespace. |
decompose_failure | Measure the numeric difference between original and corrected values: how much lies along the supplied linear rule directions (projection) and how much lies outside them (residual), with per-field contributions. Diagnostic only: it does not establish a cause, and neither record is ve |
geometric_confidence | Summarize an already-computed state_vector into a confidence level (high/medium/low) with a recommendation. Post-hoc digest - use analyze_anomaly or check_drift for fresh analysis of raw data. |
check_realization | Structural realization analysis of a payload against the Blueprint's reference configuration (requires a 'realization' block; otherwise status=skipped). Diagnostics-tier tool; prefer validate or analyze_anomaly for standard checks. |
check_drift | Check whether recent submissions still match the established pattern for this Blueprint. Returns a stability verdict and observation count. |
authorize_execution | Go/no-go for a real-world action (payment, filing, API write): runs full validation, then the Blueprint's execution gate. authorized=true only on PASS; REVIEW means do not proceed automatically. Different from validate: validate asks is this data correct, authorize_execution asks sho |
load_rule_pack | Load a prebuilt Blueprint template (invoices, timecards, legal, POs, claims). Call without pack_id to list packs; then create_blueprint to save a customized copy. |
get_execution_trace | Run validation and return the per-node execution trace (node names, deterministic flags, timing) plus the verdict and determinism hash. Use validate for normal operation; this is for debugging and audit preparation. |
verify_replay | Check replay commitment integrity and compare recorded execution components. Version 4 includes reference context and the final result/status. A match compares commitments; this tool does not rerun the workflow or reconstruct historical reference populations, and does not prove factual c |
account_status | This account's plan, key usage, Blueprint counts, and the deployed platform build fingerprint (version, build, deployed). |
delete_blueprint | Permanently delete a Blueprint and revoke its API keys. Irreversible; requires confirm=true. Account-level keys are unaffected. |
update_blueprint | Update an existing Blueprint in place. Only passed fields change; pass [] to clear a list. workflow_name cannot be renamed and existing API keys keep working. Different from create_blueprint: modifies an existing Blueprint, mints no new key. |
list_api_keys | List this account's API keys (masked) with their Blueprint bindings. |
rotate_api_key | Replace an API key with a fresh one. The old key stops working immediately; the new key inherits its bindings. |
delete_api_key | Permanently delete one of the caller's API keys. DESTRUCTIVE — agents using the deleted key will receive auth errors immediately. The Blueprint a key was tied to (if any) is NOT affected; only the credential is revoked. To delete a Blueprint and all its keys, use delete_blueprint. |