Add concise positioning copy to the website only where it helps clarify CommandLayer's value.
Core message:
Enterprise identity systems answer who an agent is inside an organization. CommandLayer answers what the agent did, who signed it, and whether anyone can independently verify the proof.
Do not name Microsoft directly in marketing copy unless used as a generic example in docs. Avoid claiming integration with Microsoft, Entra, Agent 365, or any vendor.
Preferred language:
- Enterprise identity proves who an agent is inside an organization.
- CLAS receipts prove what that agent did outside of it.
- Identity systems manage access. CommandLayer makes machine actions portable, signed, and independently verifiable.
- CommandLayer is designed to complement enterprise agent identity systems by adding portable machine-action receipts.
Suggested placements:
-
public/how-it-works.html
Section title: Identity is not enough
Copy: An agent identity can tell a system who an agent is. It does not automatically create a portable proof of what the agent did. CommandLayer receipts add the missing layer: a signed, verifiable record of a machine action that can travel across tools, organizations, APIs, and registries.
-
public/ambient-verification.html
Section title: Beyond internal logs
Copy: Internal identity and audit systems are useful inside one organization. Ambient verification is for the boundary between systems: when one agent, service, registry, or counterparty needs to verify a receipt without trusting the original platform.
-
public/commercial.html
Section title: Portable trust for autonomous software systems
Copy: Your internal identity provider can manage agent access inside your organization. CommandLayer adds portable machine-action receipts for workflows that need to be verified by external systems, auditors, counterparties, or other agents.
Constraints:
- Do not change nav.
- Do not redesign unrelated sections.
- Do not mention Microsoft as a customer or partner.
- Do not claim live enterprise integrations.
- Keep wording serious and enterprise-grade.
Acceptance criteria:
- Copy is added to the three pages above.
- Existing links and scripts remain intact.
- No unsupported vendor claims.
- Run available tests or report if no test script exists.
Add concise positioning copy to the website only where it helps clarify CommandLayer's value.
Core message:
Enterprise identity systems answer who an agent is inside an organization. CommandLayer answers what the agent did, who signed it, and whether anyone can independently verify the proof.
Do not name Microsoft directly in marketing copy unless used as a generic example in docs. Avoid claiming integration with Microsoft, Entra, Agent 365, or any vendor.
Preferred language:
Suggested placements:
public/how-it-works.html
Section title: Identity is not enough
Copy: An agent identity can tell a system who an agent is. It does not automatically create a portable proof of what the agent did. CommandLayer receipts add the missing layer: a signed, verifiable record of a machine action that can travel across tools, organizations, APIs, and registries.
public/ambient-verification.html
Section title: Beyond internal logs
Copy: Internal identity and audit systems are useful inside one organization. Ambient verification is for the boundary between systems: when one agent, service, registry, or counterparty needs to verify a receipt without trusting the original platform.
public/commercial.html
Section title: Portable trust for autonomous software systems
Copy: Your internal identity provider can manage agent access inside your organization. CommandLayer adds portable machine-action receipts for workflows that need to be verified by external systems, auditors, counterparties, or other agents.
Constraints:
Acceptance criteria: