31 docs tagged with "governance-trust"

Prompt injection, PEP bypass, manifest violations, and entitlement escalation tests for PGAR runtimes.

Immutable verdict logs, examiner questions, and replaying authorization without chat transcripts.

Curated third-party resources on PDP/PEP, OAuth, policy engines, and agent authorization, mapped to the PGAR playbook series.

What examiners get before scale: inventory row, obligation map, runtime verdict sample, eval gates.

Two views, one G.A.I.N subject: estate operating how-to and PGAR runtime how-to.

Every plan or synthesize call goes through Plane ③, then validate proposals against the manifest and gate side effects at the PEP.

No inventory, no owner, no go-live. Minimum fields for an AI use-case row before runtime scale.

Where to maintain tool manifests, how agentic apps load them, versioning and rollback, and pros and cons of repo files vs registry APIs.

Tool manifests, schema compliance, PEP gating per tool, and blocking proposals outside the registry.

Hub for G.A.I.N MCP: MCP is transport. Tool contracts (manifests) live under Agents.

Session, working, loop, episodic, and long-term memory as route policy plus a partitioned store: isolation, TTL, retrieve_only, writes, and erase.

Map each must-we obligation to a named control and an evidence artifact. Governance Operating how-to.

Estate how-to for G.A.I.N Governance: inventory, obligation-to-control map, and go-live evidence pack. Runtime PEP/PDP lives in the Runtime series.

ALLOW, DENY, and STEP_UP only — policy versioning, rule authoring, and deterministic authorization.

The four steps every Policy Enforcement Point runs on every proposal: receive, ask PDP, audit, act.

API gateway, Identity Provider, token validation, and claims issuance at the trust boundary.

Session custody, orchestration, proposal routing, and receiving results before validation or synthesis.

Tool schemas only, proposal-not-permission, and keeping authority out of the model boundary.

The policy layer — enforcement point, decision point, verdict handling, and deny-before-downstream.

Re-authorization, side-effect execution, and returning results to the agentic app, not the LLM directly.

The five PGAR trust boundaries in request order (ingress, agentic app, LLM proposal, PEP + PDP, downstream), including multi-agent workflows, with links to each implementation playbook.

Core PGAR building blocks in implementation order — SARAC contracts, token custody, PEP/PDP enforcement, step-up, and audit replay.

Subject, action, resource, and context schemas for PEP-to-PDP calls — the contracts that make verdict chains replayable.

Golden scenario libraries for PDP/PEP regression, representative, edge, adversarial, and incident replay cases.

Hub for G.A.I.N RAG playbooks: retrieval as a governed action, context packs, and PEP-gated search.

Retrieval as a PEP-gated tool, context pack logging, validation handoff, and PGAR applied to RAG.

Hub for Policy-Governed Agent Runtime playbooks (foundation, assurance, and boundary). PEP/PDP on the request path.

Two pins, durable run store, and when a checkpointer or Temporal is enough: loop bounds, credential stripping, restart by run_id.

STEP_UP verdict handling, four-eyes approval, re-evaluation with context.approval, and UX ownership in the agentic app.

What stays in the agentic app, what the LLM sees, and the PGAR test for credential isolation.

Decide-only router: freeze the route, async-start the app, skip the loop on clarify/abstain. UI and event ingress.