38 docs tagged with "agents"

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

Hub for Agents playbooks: intent routing, orchestration (session, memory, autonomy), and tool manifests.

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

Run Pattern 0-3 from the pinned route: single inference, autonomous loop, fixed workflow, or guided hybrid inside Plane ②.

How to evaluate the Tool plane — selection, arguments, idempotency, error handling, and schema compliance for agent tool calls.

How to evaluate the Memory plane — session scope, TTL, consistency, and cross-session leakage in agent and copilot systems.

How to evaluate the Action plane — policy enforcement, authorization, side effects, and auditability before irreversible operations execute.

Curated third-party articles, guides, and tool docs on LLM and agent evaluation — mapped to the Eval Framework Blueprint series.

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

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.

Hub for intent routing playbooks: route contract reference, route table lifecycle, layered classification, agentic app wiring, and routing eval CI.

Implement intent classification: eligible routes, rules (channel and event), classifier, LLM fallback, safety veto, and outcomes before the agent loop.

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.

Hub for Plane ② orchestration playbooks: session custody, memory, autonomy shape, and inference handoff after the intent router decides and the app pins the run.

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.

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

Field dictionary for route table rows: route, activation target (which agentic app to start), manifest, policy, retrieval, memory, workflow, and related artifact ids.

Where route contracts live, how to version and promote them, entitlement requirements per row, and rollback in regulated environments.

Golden intent sets, release gates, adversarial coverage, and incident replay for Plane ① routing — aligned with Eval Input plane.

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.