@intentius/chant-lexicon-cedar 0.124.31 → 0.124.33

package/dist/agentcore/embed.js

@@ -0,0 +1,250 @@
+/**
+ * Typed embedding of a cedar or dogwood policy into
+ * `AWS::BedrockAgentCore::Policy` (#1660).
+ *
+ * The aws lexicon keeps the deployment vehicle, exactly as it does for AVP
+ * (#1652, `../avp/embed.ts`). What differs is the shape of the vehicle:
+ * AgentCore's `Definition` is a two-arm `oneOf`, not the single `Static` arm
+ * `AWS::VerifiedPermissions::Policy` has —
+ *
+ * ```jsonc
+ * "PolicyDefinition": {
+ *   "oneOf": [{ "required": ["Cedar"] }, { "required": ["Policy"] }]
+ * }
+ * ```
+ *
+ * — where `Cedar.Statement` is plain Cedar and `Policy.Statement` is the
+ * language-agnostic arm. That second arm is what makes AgentCore the
+ * deployment target for the dogwood dialect: a `.dw` policy is a Cedar policy
+ * with `when temporal { … }` clauses, which the `Cedar` arm has no business
+ * accepting, and the `Policy` arm exists precisely so a policy engine can be
+ * handed something that is not plain Cedar.
+ *
+ * A project that has both lexicons installed writes
+ *
+ * ```ts
+ * new BedrockAgentCorePolicy({
+ *   PolicyEngineId: engine.ref(),
+ *   Name: "writeNeedsApproval",
+ *   ...agentCoreStagedPolicy("writeNeedsApproval", writeNeedsApproval, "log-only"),
+ * });
+ * ```
+ *
+ * and the statement is the same text `chant build` writes to `policies.dw`,
+ * rendered by the same renderer, with `@id` intact.
+ *
+ * ### Why no dependency, and why the example uses plain objects
+ *
+ * Same rule as `../avp/embed.ts` and for the same reason: a cedar → aws
+ * dependency would invert the epic's decision that Cedar is vendor-neutral and
+ * make the cedar lexicon unbuildable without the aws one. Nothing here imports
+ * `@intentius/chant-lexicon-aws`. The seam is the data shape, which is stable
+ * CloudFormation, and the prop names below are the generated class's own
+ * (`PolicyEngineId`, `Name`, `Definition`, `EnforcementMode`, `Description`),
+ * so substituting the real class is a one-line edit. `examples/agentcore-policy/`
+ * demonstrates the pairing with a plain-object stand-in, because the shipped
+ * cedar examples build against the cedar serializer alone and an `AWS::*` entity
+ * declared in that tree would have no serializer to emit it.
+ *
+ * ### What this module refuses
+ *
+ * Templates. `AWS::VerifiedPermissions::Policy` has a `TemplateLinked` arm;
+ * AgentCore's `Definition` union does not, so a statement carrying a
+ * `?principal` or `?resource` slot has nowhere to go and would be rejected at
+ * deploy time with an error about the policy text rather than about the slot.
+ * {@link agentCoreStatement} throws instead, at authoring time, naming the
+ * declaration.
+ */
+import { isDeclarable } from "@intentius/chant/declarable";
+import { cedarPolicyRecords, getProps, renderPolicyText, resolvePolicyId, CEDAR_POLICY_TYPE, } from "../serializer.js";
+import { dogwoodPolicyRecords, renderTemporalPolicyText } from "../dogwood/serialize.js";
+import { DOGWOOD_POLICY_TYPE } from "../dogwood/policy.js";
+import { enforcementMode } from "./enforcement.js";
+// ── Upstream's own limits ─────────────────────────────────────────
+/** `Statement` minLength, on both arms of the union. */
+export const AGENTCORE_STATEMENT_MIN = 35;
+/** `Statement` maxLength, on both arms of the union. */
+export const AGENTCORE_STATEMENT_MAX = 10000;
+/** `Name` — an identifier, and create-only, so a rename replaces the policy. */
+export const AGENTCORE_NAME_PATTERN = /^[A-Za-z][A-Za-z0-9_]*$/;
+/**
+ * `?principal` / `?resource` — Cedar's two template slots.
+ *
+ * Scanned over the whole statement rather than only the scope positions, which
+ * is where a slot can legally appear. Inside a `temporal { … }` clause the `?`
+ * sigil means a macro parameter, so in principle a macro parameter named
+ * `?principal` would read as a slot here — but macro parameters are legal only
+ * inside a macro *definition* body, and this module renders policies, never
+ * definitions. There is nowhere in a policy statement for the pattern to mean
+ * anything else.
+ */
+const TEMPLATE_SLOT = /\?(?:principal|resource)\b/;
+// ── Rendering ─────────────────────────────────────────────────────
+/** The dialect keys `TemporalPolicyProps` adds to `CedarPolicyProps`. */
+const DOGWOOD_ONLY_PROPS = ["whenTemporal", "unlessTemporal", "whenGuardrails", "unlessGuardrails"];
+function hasTemporalProps(props) {
+    return DOGWOOD_ONLY_PROPS.some((key) => {
+        const value = props[key];
+        return Array.isArray(value) ? value.length > 0 : value !== undefined;
+    });
+}
+function renderRecord(name, props, options) {
+    const temporal = hasTemporalProps(props);
+    const id = options.policyId ?? resolvePolicyId(name, props);
+    return { text: temporal ? renderTemporalPolicyText(id, props) : renderPolicyText(id, props), temporal };
+}
+/**
+ * Every policy in a build, as one statement.
+ *
+ * Cedar policies first, then temporal ones, both in declaration order, so the
+ * text is stable across builds. Any temporal policy in the set puts the whole
+ * statement in the `Policy` arm — which is correct rather than a compromise: a
+ * `.dw` file holds plain Cedar policies too, and splitting the set across two
+ * AgentCore policies to keep one of them in the `Cedar` arm would give the two
+ * halves separate `EnforcementMode` dials for no reason.
+ */
+function renderPolicySet(entities) {
+    const parts = [];
+    for (const { id, props } of cedarPolicyRecords(entities))
+        parts.push(renderPolicyText(id, props));
+    const temporalRecords = dogwoodPolicyRecords(entities);
+    for (const { id, props } of temporalRecords)
+        parts.push(renderTemporalPolicyText(id, props));
+    return { text: parts.join("\n\n"), temporal: temporalRecords.length > 0 };
+}
+function render(name, source, options) {
+    if (source instanceof Map)
+        return renderPolicySet(source);
+    if (isDeclarable(source)) {
+        if (source.entityType !== CEDAR_POLICY_TYPE && source.entityType !== DOGWOOD_POLICY_TYPE) {
+            throw new Error(`cedar: "${name}" is a ${source.entityType}, which is not a policy — AWS::BedrockAgentCore::Policy embeds ${CEDAR_POLICY_TYPE} or ${DOGWOOD_POLICY_TYPE}.`);
+        }
+        // Read straight off the entity: no reference walk, because a single
+        // Declarable carries no map of the names its siblings were declared under.
+        // A scope that names another declared entity needs the policy-set form,
+        // which walks references the way the serializer does.
+        const props = getProps(source);
+        const temporal = source.entityType === DOGWOOD_POLICY_TYPE || hasTemporalProps(props);
+        const id = options.policyId ?? resolvePolicyId(name, props);
+        return { text: temporal ? renderTemporalPolicyText(id, props) : renderPolicyText(id, props), temporal };
+    }
+    return renderRecord(name, source, options);
+}
+function assertEmbeddable(name, statement) {
+    if (statement.text.length === 0) {
+        throw new Error(`cedar: "${name}" rendered no policy text, so there is nothing for AgentCore to evaluate.`);
+    }
+    if (TEMPLATE_SLOT.test(statement.text)) {
+        throw new Error(`cedar: the statement for "${name}" carries a Cedar template slot — AWS::BedrockAgentCore::Policy takes a static statement, and its Definition union has no template-linked arm. Write the ?principal/?resource slot as a concrete entity, or deploy the template through AWS::VerifiedPermissions::Policy instead.`);
+    }
+    if (statement.text.length < AGENTCORE_STATEMENT_MIN) {
+        throw new Error(`cedar: the statement for "${name}" is ${statement.text.length} characters and AgentCore's minimum is ${AGENTCORE_STATEMENT_MIN}.`);
+    }
+    if (statement.text.length > AGENTCORE_STATEMENT_MAX) {
+        throw new Error(`cedar: the statement for "${name}" is ${statement.text.length} characters and AgentCore's maximum is ${AGENTCORE_STATEMENT_MAX} — split it across policies, each with its own EnforcementMode.`);
+    }
+}
+// ── The seam ──────────────────────────────────────────────────────
+/**
+ * The policy text for one AgentCore policy — the exact string a `Statement`
+ * wants, on whichever arm it lands.
+ *
+ * `name` is the chant entity name; the `@id` annotation the statement carries
+ * is derived from it the same way the serializer derives it, so the statement
+ * in the policy engine can be matched back to the declaration that produced it.
+ */
+export function agentCoreStatement(name, source, options = {}) {
+    const statement = render(name, source, options);
+    assertEmbeddable(name, statement);
+    return statement.text;
+}
+/**
+ * The `Definition` property of `AWS::BedrockAgentCore::Policy`.
+ *
+ * The arm is chosen by what the policy is: a `Dogwood::TemporalPolicy`, or any
+ * props carrying a temporal clause, lands in `Definition.Policy`; plain Cedar
+ * lands in `Definition.Cedar`. `options.language` overrides in the one
+ * direction that is safe (see {@link AgentCoreEmbedOptions.language}).
+ */
+export function agentCorePolicyDefinition(name, source, options = {}) {
+    const statement = render(name, source, options);
+    assertEmbeddable(name, statement);
+    if (options.language === "cedar" && statement.temporal) {
+        throw new Error(`cedar: "${name}" has temporal clauses, so it cannot go in Definition.Cedar — that arm is plain Cedar, and AgentCore's Cedar parser has no \`when temporal\` rule. Drop \`language: "cedar"\` and it lands in Definition.Policy.`);
+    }
+    const dogwood = options.language === "dogwood" || (options.language === undefined && statement.temporal);
+    return dogwood ? { Policy: { Statement: statement.text } } : { Cedar: { Statement: statement.text } };
+}
+/**
+ * A policy and its rollout stage, ready to spread into the generated class.
+ *
+ * The staged-rollout pattern in one call, which is the point (#1660): shipping
+ * log-only and promoting to enforcing is a one-token diff, not a hand-edited
+ * `EnforcementMode` string somewhere else in the template. See
+ * ./enforcement.ts for why observe-before-enforce is the default reading of a
+ * temporal policy rather than an optional nicety.
+ */
+export function agentCoreStagedPolicy(name, source, stage, options = {}) {
+    return {
+        Name: agentCorePolicyName(name),
+        Definition: agentCorePolicyDefinition(name, source, options),
+        EnforcementMode: enforcementMode(stage),
+        ...(options.description ? { Description: options.description } : {}),
+    };
+}
+/**
+ * Every required prop of `AWS::BedrockAgentCore::Policy`, plus the stage.
+ *
+ * `PolicyEngineId` is a string here rather than an AttrRef because this module
+ * does not know the aws lexicon's reference types. A project passes
+ * `engine.ref()` in place of the literal and TypeScript is satisfied by the
+ * generated class's own prop type, not by this one.
+ */
+export function agentCorePolicyResource(name, source, policyEngineId, options = {}) {
+    const { stage, ...embed } = options;
+    return {
+        PolicyEngineId: policyEngineId,
+        Name: agentCorePolicyName(name),
+        Definition: agentCorePolicyDefinition(name, source, embed),
+        ...(stage ? { EnforcementMode: enforcementMode(stage) } : {}),
+        ...(embed.description ? { Description: embed.description } : {}),
+    };
+}
+/**
+ * Every policy in a build, as one AgentCore `Definition` each, keyed by chant
+ * entity name.
+ *
+ * The whole-set form, and the one that walks references between declared
+ * entities — that is what `cedarPolicyRecords`/`dogwoodPolicyRecords` do. One
+ * definition per policy rather than one merged statement, because
+ * `EnforcementMode` is a per-policy dial and merging would throw it away; hand
+ * the map to {@link agentCorePolicyDefinition} instead when a single AgentCore
+ * policy really should carry the whole set.
+ */
+export function agentCorePolicySet(entities, options = {}) {
+    const out = {};
+    for (const { name, id, props } of cedarPolicyRecords(entities)) {
+        out[name] = agentCorePolicyDefinition(name, props, { ...options, policyId: id });
+    }
+    for (const { name, id, props } of dogwoodPolicyRecords(entities)) {
+        out[name] = agentCorePolicyDefinition(name, props, { ...options, policyId: id, language: "dogwood" });
+    }
+    return out;
+}
+/**
+ * The chant entity name as an AgentCore `Name`.
+ *
+ * `Name` is create-only and matches `^[A-Za-z][A-Za-z0-9_]*$` — no hyphens,
+ * which is why it is not the kebab-case policy id the `@id` annotation carries.
+ * Checked rather than coerced: silently rewriting a name that is create-only
+ * would mean a later rename replaces the policy without anyone having asked.
+ */
+export function agentCorePolicyName(name) {
+    if (!AGENTCORE_NAME_PATTERN.test(name)) {
+        throw new Error(`cedar: "${name}" is not a legal AWS::BedrockAgentCore::Policy Name — it must match ${AGENTCORE_NAME_PATTERN.source} (letters, digits and underscores, starting with a letter).`);
+    }
+    if (name.length > 48) {
+        throw new Error(`cedar: the AgentCore policy Name "${name}" is ${name.length} characters and the maximum is 48.`);
+    }
+    return name;
+}

package/dist/agentcore/enforcement.js

@@ -0,0 +1,81 @@
+/**
+ * `EnforcementMode` — the dial that makes a policy rollout observable before it
+ * is binding (#1660).
+ *
+ * `AWS::BedrockAgentCore::Policy` carries an optional `EnforcementMode` with
+ * exactly two values, and the CloudFormation schema says what they mean:
+ *
+ * > Whether the policy contributes to the enforce decision returned to Gateway.
+ * > LOG_ONLY policies are still evaluated but their decisions are observed
+ * > only, allowing customers to validate a policy against real traffic before
+ * > promoting it.
+ *
+ * That is observe-before-enforce, in the substrate, per policy — the same shape
+ * chant already has at the ops layer, and the reason epic #1646 picked
+ * AgentCore as the deployment target for the temporal dialect rather than
+ * inventing a staging mechanism. A temporal policy is the case that needs it
+ * most: `formerly within 24h …` cannot be reasoned about from the source alone,
+ * because whether it fires depends on traffic nobody has replayed yet.
+ *
+ * ### The two names, and why chant does not reuse AWS's
+ *
+ * The wire values are `LOG_ONLY` and `ACTIVE`. `ACTIVE` is a poor name for
+ * "enforcing" — it reads as "not disabled", and `LOG_ONLY` is active too; it is
+ * evaluated on every request. So the authoring vocabulary here is
+ * `"log-only"` / `"enforce"`, and {@link enforcementMode} is the one place the
+ * translation happens. The wire values are exported as well, for a caller that
+ * has one in hand from a live read.
+ *
+ * ### The showcase seam
+ *
+ * A staged policy rollout has to be demonstrable end to end: ship the policy
+ * log-only, watch what it would have denied, promote it. This module is that
+ * seam. The whole rollout is one argument —
+ * `agentCoreStagedPolicy(name, policy, stage)` — so the promotion is a
+ * one-token diff a reviewer can see, rather than a hand-edited string in a
+ * CloudFormation resource. Anything more elaborate (which environments are
+ * promoted, who decides) belongs to the caller's own config; this module's job
+ * is to make the two states nameable and the transition legible.
+ */
+/**
+ * The wire values `EnforcementMode` takes, keyed by the stage they implement.
+ *
+ * A typed constant pair rather than a bare union so a caller reads
+ * `AGENTCORE_ENFORCEMENT.logOnly` at the call site and cannot typo the string.
+ */
+export const AGENTCORE_ENFORCEMENT = {
+    /** Evaluated on every request; its decision is observed, never returned. */
+    logOnly: "LOG_ONLY",
+    /** Contributes to the decision Gateway returns. AWS's own default. */
+    enforce: "ACTIVE",
+};
+/**
+ * The `EnforcementMode` a stage deploys as.
+ *
+ * Omitting `EnforcementMode` entirely is legal and means `ACTIVE` — AWS's
+ * schema declares that default. This helper never returns `undefined`, so a
+ * policy that went through it says which stage it is in on the face of the
+ * template, and a diff that promotes one shows the change.
+ */
+export function enforcementMode(stage) {
+    return stage === "log-only" ? AGENTCORE_ENFORCEMENT.logOnly : AGENTCORE_ENFORCEMENT.enforce;
+}
+/** The stage a wire value came from — the inverse of {@link enforcementMode}. */
+export function enforcementStage(mode) {
+    return mode === AGENTCORE_ENFORCEMENT.logOnly ? "log-only" : "enforce";
+}
+/** True when the policy's decision reaches Gateway rather than only the log. */
+export function isEnforcing(mode) {
+    return enforcementStage(mode) === "enforce";
+}
+/**
+ * One line of prose for a stage, for a description or a plan summary.
+ *
+ * Kept here rather than at the call sites so every surface that explains a
+ * staged policy explains it the same way.
+ */
+export function describeStage(stage) {
+    return stage === "log-only"
+        ? "Evaluated against real traffic; decisions are logged and do not affect the response."
+        : "Enforcing: this policy's decision reaches the gateway.";
+}

package/dist/agentcore/scan.js

@@ -0,0 +1,93 @@
+/**
+ * Finding embedded AgentCore policy statements in a build's emitted output
+ * (#1660).
+ *
+ * The DWD walls read emitted *text* rather than the in-memory model, for the
+ * reason `../dogwood/scan.ts` sets out: `chant audit` runs over artifacts chant
+ * did not write, and a wall that only fires on chant's own output is not a
+ * wall. An embedded statement is the same situation one lexicon further out —
+ * the statement lands in whatever the aws lexicon emitted, so this reads the
+ * emitted template rather than reaching for a resource class the cedar lexicon
+ * deliberately does not import.
+ *
+ * Structural, not CloudFormation-specific. The thing being looked for is an
+ * object with a `Definition.Policy.Statement` string, which is AgentCore's
+ * language-agnostic arm wherever it appears — in a CFN template's
+ * `Resources.<id>.Properties`, in a plan JSON, in a fixture. The nearest
+ * enclosing key is carried along as the name to blame, which for a CFN template
+ * is the logical id.
+ */
+import { isRecord } from "../policy-text.js";
+function walk(node, logicalId, found) {
+    if (Array.isArray(node)) {
+        for (const item of node)
+            walk(item, logicalId, found);
+        return;
+    }
+    if (!isRecord(node))
+        return;
+    const definition = node.Definition;
+    if (isRecord(definition)) {
+        for (const arm of ["Cedar", "Policy"]) {
+            const value = definition[arm];
+            if (isRecord(value) && typeof value.Statement === "string") {
+                found.push({ ...(logicalId ? { logicalId } : {}), arm, statement: value.Statement });
+            }
+        }
+    }
+    for (const [key, value] of Object.entries(node)) {
+        // `Properties` is CloudFormation's own wrapper, so it is not the name to
+        // blame — the logical id one level up is.
+        walk(value, key === "Properties" ? logicalId : key, found);
+    }
+}
+/** Every emitted text in a build, with the lexicon and filename that carried it. */
+function emittedTexts(ctx) {
+    const out = [];
+    for (const [lexicon, output] of ctx.outputs) {
+        if (typeof output === "string") {
+            if (output.length > 0)
+                out.push({ lexicon, source: lexicon, text: output });
+            continue;
+        }
+        if (typeof output.primary === "string" && output.primary.length > 0) {
+            out.push({ lexicon, source: lexicon, text: output.primary });
+        }
+        for (const [filename, content] of Object.entries(output.files ?? {})) {
+            if (typeof content === "string")
+                out.push({ lexicon, source: filename, text: content });
+        }
+    }
+    return out;
+}
+/**
+ * Every AgentCore policy definition embedded in a build's emitted output.
+ *
+ * Non-JSON output is skipped rather than reported: most emitted files are not
+ * JSON, and a parse failure here says nothing about whether a statement is
+ * there.
+ */
+export function embeddedAgentCoreDefinitions(ctx) {
+    const results = [];
+    for (const { lexicon, source, text } of emittedTexts(ctx)) {
+        const trimmed = text.trimStart();
+        if (!trimmed.startsWith("{") && !trimmed.startsWith("["))
+            continue;
+        let parsed;
+        try {
+            parsed = JSON.parse(text);
+        }
+        catch {
+            continue;
+        }
+        const found = [];
+        walk(parsed, undefined, found);
+        for (const hit of found)
+            results.push({ lexicon, source, ...hit });
+    }
+    return results;
+}
+/** Only the language-agnostic arm — the one a `.dw` statement travels in. */
+export function embeddedAgentCorePolicyStatements(ctx) {
+    return embeddedAgentCoreDefinitions(ctx).filter((d) => d.arm === "Policy");
+}

package/dist/avp/ambient.js

@@ -0,0 +1,100 @@
+/**
+ * Policies that are simply *there* (#1652, chant #1278).
+ *
+ * For most lexicons ambient discovery is housekeeping — an unattached security
+ * group, an orphaned volume. For an authorization store it is a security
+ * finding. A policy in the store that no chant entity declares is a grant
+ * nobody in the source tree can see: it was added in the console, or by a
+ * previous tool, or by a teammate's script, and it is being evaluated on every
+ * request. `describeResources` structurally cannot report it, because it
+ * resolves outward from what was declared and this is precisely what was not.
+ *
+ * The reader reports the policy and its statement. It does not decide that an
+ * ambient `permit` is dangerous — that is a conclusion, and putting conclusions
+ * in observations is the mistake chant #1271 undid. What it does carry is the
+ * `effect`, because "which ambient policies are permits" is the first question
+ * anyone asks and re-parsing the statement to answer it is work every consumer
+ * would repeat.
+ */
+import { CEDAR_POLICY_TYPE } from "../serializer.js";
+import { credentialsAvailable } from "./client.js";
+import { ownershipFromDescription } from "./ownership.js";
+import { loadLivePolicies, resolvePolicyStoreId } from "./store.js";
+import { effectFromStatement } from "./statement.js";
+/**
+ * The kinds this lexicon can enumerate beyond the declared estate.
+ *
+ * One, and it is the only kind cedar deploys. Declared separately from the
+ * reader so `chant search` can say `--ambient` is relevant to a policy query
+ * without paying for a scan to find out.
+ */
+export const AVP_AMBIENT_KINDS = [CEDAR_POLICY_TYPE];
+/**
+ * Policies in the store that nothing declares and nothing already observed.
+ *
+ * Best-effort by contract: ambient discovery is additive, and a failure here
+ * must not sink a managed observation that already succeeded, so the whole scan
+ * degrades to `{}` rather than throwing. The managed answer is complete without
+ * any of this.
+ */
+export async function observeAvpAmbient(options) {
+    if (!options.kinds.includes(CEDAR_POLICY_TYPE))
+        return {};
+    const env = options.env ?? process.env;
+    const policyStoreId = resolvePolicyStoreId({
+        environment: options.environment,
+        ...(options.policyStoreId ? { policyStoreId: options.policyStoreId } : {}),
+        ...(options.entities ? { entities: options.entities } : {}),
+        env,
+    });
+    if (!policyStoreId || !credentialsAvailable(env))
+        return {};
+    let policies;
+    try {
+        policies = await loadLivePolicies({
+            policyStoreId,
+            ...(options.client ? { client: options.client } : {}),
+            withStatements: true,
+        });
+    }
+    catch {
+        return {};
+    }
+    // Two exclusions, because "managed" has two spellings here: the AVP policy id
+    // the observation recorded as a physicalId, and the Cedar id the source
+    // declares. A declared policy whose read failed has no physicalId, and
+    // calling it ambient would turn a hole into a security finding.
+    const observedIds = new Set(Object.values(options.observed)
+        .map((meta) => meta.physicalId)
+        .filter((id) => typeof id === "string" && id.length > 0));
+    const declaredIds = new Set(options.declaredPolicyIds ?? []);
+    const ambient = {};
+    for (const policy of policies) {
+        if (observedIds.has(policy.policyId))
+            continue;
+        if (policy.cedarPolicyId !== undefined && declaredIds.has(policy.cedarPolicyId))
+            continue;
+        const effect = policy.statement ? effectFromStatement(policy.statement) : undefined;
+        ambient[`policy/${policy.policyId}`] = {
+            type: CEDAR_POLICY_TYPE,
+            status: policy.policyType || "STATIC",
+            physicalId: policy.policyId,
+            ...(policy.lastUpdatedDate ? { lastUpdated: policy.lastUpdatedDate } : {}),
+            ownership: ownershipFromDescription(policy.description),
+            ambient: true,
+            attributes: {
+                policyStoreId: policy.policyStoreId,
+                policyId: policy.policyId,
+                policyType: policy.policyType,
+                ...(effect ? { effect } : {}),
+                ...(policy.cedarPolicyId ? { cedarPolicyId: policy.cedarPolicyId } : {}),
+                ...(policy.authoredDescription ? { description: policy.authoredDescription } : {}),
+                // The statement itself, so the consumer can judge the grant rather than
+                // trusting a summary this reader invented.
+                ...(policy.statement ? { statement: policy.statement } : {}),
+                ...(policy.createdDate ? { createdDate: policy.createdDate } : {}),
+            },
+        };
+    }
+    return ambient;
+}