Skip to main content

​
Organization Card Templates

Organization card templates require an Enterprise plan. Contact sales to enable this feature.
Org card templates let you define a base alignment card that every agent in your organization inherits. The template is immutable from the agent’s perspective — agents can add to it but cannot remove anything the org defines. This ensures consistent alignment policy across your entire agent fleet.

​
How It Works

The org card template establishes a floor for alignment policy. Every agent’s canonical card is computed by composing the org template with the agent’s individual card: 
Org Template (base) + Agent Card (additive) = Canonical Card (used for verification)
The org template defines the non-negotiable alignment requirements. Individual agent cards add agent-specific values, actions, and triggers on top. This is similar to how an organization might have company-wide policies that every employee follows, while individual teams add their own domain-specific guidelines.

​
Setting Up

2
Open the Mnemom dashboard, click your organization name in the sidebar, and select Settings.
3
Open the Alignment Card Template section
4
Scroll to the Alignment Card Template panel. If this is your first time, the template is disabled and empty.
5
Enable the template
6
Toggle the Enable org card template switch. This activates template composition for all agents in the org.
7
Configure the template
8
Use the Visual editor for a guided experience or switch to the JSON editor for full control.
9
At minimum, define:
10
  • Values: Core organizational values that every agent must declare
  • Forbidden actions: Actions no agent in the org should ever take
  • Audit commitment: Minimum audit requirements (retention, queryability, tamper evidence)
    • 11
    Save and verify
    12
    Click Save. The template is validated before saving. Once saved, all agents in the org immediately inherit the template values in their canonical cards.
    13
    Verify by checking any agent’s card via smoltbot card show or the dashboard — you should see the org template values included.

    ​
    Visual Editor vs JSON Editor

    The visual editor provides form-based inputs for each card block with inline validation. Use it for initial setup and when making incremental changes. The JSON editor shows the raw template JSON. Use it for bulk edits, copying from a file, or when you need precise control over the template structure.
    Both editors validate on save. The JSON editor is faster for teams that maintain their org template in version control and paste updates from a file.

    ​
    Composition Rules

    When the org template is active, each field in the canonical card is computed according to these rules:
    Card FieldComposition RuleExample
    values.declaredUnion of org + agent valuesOrg: [honesty, transparency] + Agent: [editorial_independence] = [honesty, transparency, editorial_independence]
    values.definitionsMerged. Agent definitions cannot override org definitionsOrg defines honesty; agent can define editorial_independence but not redefine honesty
    values.hierarchyOrg hierarchy takes precedence if definedOrg sets lexicographic; agent cannot change to weighted
    values.conflicts_withUnion of org + agent conflictsOrg: [deception] + Agent: [upsell_pressure] = [deception, upsell_pressure]
    autonomy_envelope.bounded_actionsAgent-specific (org does not restrict)Agent defines its own bounded actions
    autonomy_envelope.forbidden_actionsUnion of org + agent forbidden actionsOrg: [exfiltrate_data] + Agent: [delete_records] = [exfiltrate_data, delete_records]
    autonomy_envelope.escalation_triggersUnion of org + agent triggersOrg triggers always apply; agent adds more
    audit_commitment.retention_daysMaximum of org and agent valueOrg: 180 days, Agent: 365 days = 365 days
    audit_commitment.queryableOrg true cannot be overridden to falseIf org requires queryable, all agents are queryable
    audit_commitment.tamper_evidenceStrongest mechanism wins (merkle > signed > append_only)Org: signed, Agent: merkle = merkle
    Composition is always additive from the agent’s perspective. Agents can strengthen alignment requirements but never weaken them below the org floor.

    ​
    Agent Exemptions

    In rare cases, an agent may need to operate without the org template. For example, a testing agent that intentionally exercises boundary conditions, or an agent operating under a different regulatory framework.

    ​
    Exemption Flow

    Exemptions require a double-confirm process:
    1
    Request exemption
    2
    Navigate to the agent’s page in the dashboard. In the Alignment Card section, click Request Org Template Exemption.
    3
    Provide a reason
    4
    Enter a written reason for the exemption. This is required and stored in the audit trail. Be specific — “for testing” is less useful than “this agent runs adversarial alignment tests and needs to declare conflicting values.”
    5
    Confirm
    6
    A second confirmation dialog appears with a summary of what the exemption means:
    7
  • The agent will no longer inherit org template values
  • The agent’s individual card becomes its entire canonical card
  • The exemption is logged in the org’s audit trail with your identity and reason
    • 8
    Click Confirm Exemption to proceed.

    ​
    Requirements

    • Role: Owner or admin role required
    • Audit trail: Every exemption (grant and revoke) is logged with actor, reason, and timestamp
    • Visibility: Exempted agents are flagged in the dashboard and API responses

    ​
    Revoking an Exemption

    To restore org template inheritance, navigate to the agent’s page and click Revoke Exemption in the Alignment Card section. The agent’s canonical card immediately recomposes with the org template.

    ​
    API

    You can also manage exemptions via the API: 
    # Set exemption
curl -X PUT https://api.mnemom.ai/v1/agents/{agent_id}/org-card-exempt \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"exempt": true, "reason": "Adversarial alignment testing agent"}'

# Remove exemption
curl -X PUT https://api.mnemom.ai/v1/agents/{agent_id}/org-card-exempt \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"exempt": false}'
    See the API reference for full details.

    ​
    Relationship to Conscience Values

    Org card templates and custom conscience values are complementary features that operate at different layers:
    FeatureWhat It ControlsWhen It Applies
    Org card templateThe alignment card (values, boundaries, audit commitment)At card composition time and during AAP verification
    Custom conscience valuesThe conscience prompt used by AIP for real-time integrity checksAt every AIP integrity checkpoint
    Think of it this way:
    • The org card template defines what your agents declare they will do (their alignment posture)
    • Custom conscience values define what AIP looks for when evaluating whether agents are actually doing it (the evaluation criteria)
    Both work together to create a comprehensive organizational alignment policy. The card template sets the declared boundaries; conscience values ensure those boundaries are enforced during real-time analysis.
    You can use one without the other. An org that only sets conscience values gets real-time evaluation policy without modifying agent cards. An org that only sets a card template gets consistent declared alignment without customizing the evaluation criteria.