This page describes AAES Govern’s controls. AAES Operate has private-work permissions, operational reviews and recorded-spend limits; it does not include Govern. About AAES Govern
Before you enable this package
The statement allowlist lives with the deployment's SQL adapter, not in this pack: a capability named row.insert is a promise about the statement the adapter will permit. Review the role's GRANTs and the adapter's allowlist before enabling a write. DB_HOST and DB_NAME are placeholders.
Read each action's effects and exclusions below. Before installation, also read the complete package requirements, including credential issuance, scope, expiry, and provider permissions. These are deployment prerequisites, not capabilities this package supplies.
Capabilities (6)
Each capability below is one registered operation. The complete package JSON includes its exact network destination allowlist. The repository stores it at packs/postgres.json and embeds a copy in the release binary.
Risk tiers. R0 is the minimum for reads. R2 is the minimum for write, create, update, execute, and invoke. R3 is the minimum for delete, send, pay, deploy, approve, share, and transfer. Operators can raise these levels. A minimum tier does not measure the operation's business or confidentiality risk.
On supported execution paths routed through AAES Govern, the R3 actions listed below require approval by an authorized person. Bypass paths and observation-only registrations are outside that guarantee. A provider's restoration feature does not remove this approval requirement. A provider-side approval, such as approving a GitLab merge request, is also separate from AAES Govern human approval. The capability matrix shows which execution paths are implemented, restricted to lab use, or refused at startup. Live compatibility must be tested in your environment.
Field guide. Endpoint is the service address and request method. Connector is the adapter that makes the call. Custody describes how the credential is held; the credential reference identifies the value to resolve. Data class sets handling requirements: pii means personal data, financial means financial records, and internal means internal organizational data.
postgres.invoices.query v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
query postgres://DB_HOST:5432/DB_NAME- Connector
- sql
- Custody
- customer_vault
- Credential ref
secret-ref-postgres-role- Data class
- internal
Query invoices.
Run an allowlisted SELECT against the invoices table. DB_HOST and DB_NAME are placeholders.
postgres.customers.query v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
query postgres://DB_HOST:5432/DB_NAME- Connector
- sql
- Custody
- customer_vault
- Credential ref
secret-ref-postgres-role- Data class
- pii
Query customers.
Run an allowlisted SELECT against the customers table (public.customers, the postgres-customers resource), which holds personal data.
postgres.audit_log.query v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
query postgres://DB_HOST:5432/DB_NAME- Connector
- sql
- Custody
- customer_vault
- Credential ref
secret-ref-postgres-role- Data class
- internal
Query audit log.
Run an allowlisted SELECT against the audit_log table.
postgres.row.insert v1.0.0R2
- Kind
- tool
- Action
- create
- Endpoint
exec postgres://DB_HOST:5432/DB_NAME- Connector
- sql
- Custody
- customer_vault
- Credential ref
secret-ref-postgres-role- Data class
- internal
Insert row.
Run an allowlisted INSERT against invoices. The deployment's SQL adapter must allow the exact statement; the capability registration names the operation and does not supply that statement control.
postgres.row.update v1.0.0R2
- Kind
- tool
- Action
- update
- Endpoint
exec postgres://DB_HOST:5432/DB_NAME- Connector
- sql
- Custody
- customer_vault
- Credential ref
secret-ref-postgres-role- Data class
- internal
Update row.
Run an allowlisted UPDATE against invoices. Registered at the R2 minimum tier for update. Changes to financial records may be irreversible in practice; assess that risk separately and enforce the adapter's statement allowlist.
postgres.row.delete v1.0.0R3
- Kind
- tool
- Action
- delete
- Endpoint
exec postgres://DB_HOST:5432/DB_NAME- Connector
- sql
- Custody
- customer_vault
- Credential ref
secret-ref-postgres-role- Data class
- internal
Delete row.
Run an allowlisted DELETE against the invoices table. Delete is one of the designated actions requiring human approval, so the operator approval gate applies.
On supported execution paths mediated by AAES Govern, irreversible actions require approval by an authorized person; this does not prevent calls through bypass or observation-only paths.
Credential reference
The credential field names a reference rather than containing credential material. Packs are designed not to contain secrets; the format checks cover only known credential formats and cannot prove that arbitrary text contains no secrets. Installing a package registers its capabilities. Configure the provider credentials, endpoints, and network access, then test the integration in your environment before enabling it.
- Reference
secret-ref-postgres-role- Custody
- customer_vault
- Injection
- header (Authorization)
Configure the value and injection format specified in the package. Assign responsibility for credential rotation and revocation, restrict provider permissions, and keep credential material out of logs and responses.
Complete credential requirements
A dedicated least-privilege database role held in the client's own secret manager. The SQL adapter presents the resolved material to the database as its rail requires, and never interpolates it into a statement. The role's GRANTs, and the driver's statement allowlist, are the two things to review before enabling.
Resources
postgres-invoices(table, internal):postgres://DB_HOST:5432/DB_NAME/public.invoicespostgres-customers(table, pii):postgres://DB_HOST:5432/DB_NAME/public.customerspostgres-audit-log(table, internal):postgres://DB_HOST:5432/DB_NAME/public.audit_log
Technical package and review record
Complete provider requirements and exclusions
Read operations are registered at R0, inserts and updates at R2, and deletion at R3. On supported execution paths mediated by AAES Govern, delete requires approval by an authorized person; bypass and observation-only paths are outside that guarantee.
The SQL connector uses query or exec as its method vocabulary, rather than HTTP methods. It rejects operations outside that vocabulary. The domain layer requires registration of the operation.
Exact statements are controlled by the deployment's driver adapter allowlist, rather than this package. Review that allowlist and the database role's GRANTs before enabling writes. A capability named row.insert identifies an intended operation; the adapter must enforce the corresponding statement restriction.
Download the complete package JSON for exact network allowlists, credential requirements, exclusions, and setup notes. Read these requirements before installation.
The full documentation review record is supplied in the evaluation package. The evaluation package runs in your environment and comes only with the paid design partnership. This page reproduces the source links and review block; the full record is available for evaluation. Discuss a design partnership to inspect it before installation.
Review block
This section reproduces the review block recorded in the pack file. The evidence and approval record is separate: for a reviewed pack, it is in the evaluation materials and in the release binary's embedded assets.
Review completed: 2026-10-22
2 sources, retrieved 2026-09-20
- https://www.postgresql.org/docs/current/protocol-overview.html (retrieved 2026-09-20)
- https://www.postgresql.org/docs/current/protocol-flow.html (retrieved 2026-09-20)
Current documentation links are navigation aids. They do not change the package, its historical sources or its review date. Review dates describe a documentation review, not a live integration test. No package is provider-endorsed or yet tested against a live provider tenant.
Release identity
SHA-256 of the pack file bytes: 29b12fd877828fa8b22087af57078939be989eb2bf0fd6f41edd1032227af0c8
Distributable: yes, digest matches the release manifest. Editing a package changes its release identity. A deployment plan checks its own file digests; it does not restore reviewed status or authenticate approval.