internal/

Package aggregate presents many downstream servers as one tool catalog.

Package app is the composition root.

Package audit writes a structured, post-redaction record for every call through an asynchronous single-writer pipeline, so audit I/O never sits on the request hot path (design §5, §8, ADR-0010).

Package config loads, defaults, and validates the gateway's declarative YAML configuration.

Package domain holds the shared value types and port interfaces that cross Portcullis package boundaries.

Package edge is the client-facing side of the gateway.

Package guard enforces Portcullis's internal import DAG (design §3).

Package metrics exposes the gateway's Prometheus instrumentation on /metrics.

Package pipeline composes the per-call security chain.

Package policy is the deny-by-default access engine.

Package redact performs outbound redaction of sensitive values from byte payloads (tool results, JSON-RPC errors, and notifications) before they leave the gateway or are written to the audit log.

Package registry manages the gateway's downstream MCP sessions: a bounded, supervised stdio subprocess pool per downstream plus remote HTTP sessions (design §4, §6.1, ADR-0002/0004/0006).

Package resilience provides failure-class-aware circuit breaking (design §5, ADR-0005).

Package secrets injects gateway-held downstream credentials.

Package watch polls a single file and reports content changes via a callback.