Trust Framework / Issuer PolicyMarco de confianza y política del emisor

This framework describes what the CORTEX Seal issuer checks, what it does not check, and the obligations of everyone who relies on it. It is public, versioned and modelled on the practice statements that public issuing authorities publish for the same reason: so that a relying party can decide how much weight to give the artefact.

Agent, Manifest, manifestHash, Autonomy Level A0–A5 (a proprietary scale, published as an open specification), Credential, Seal, Status List and Binding have the meanings given in the Terms of Service and in the public specification.

A CORTEX Seal credential attests that (i) an identified legal person declared the content of the Manifest, (ii) the declaration was signed by the CORTEX Seal issuer at a given time, (iii) the Manifest has not changed since, as evidenced by manifestHash, and (iv) the credential has not been revoked as of the moment of verification.

It does not attest that the declaration is true, that the agent behaves as declared, that the agent is safe, or that it complies with any law.

Identification of the Tenant as a legal person and verification of its control over the domain shown; designation to Cosmolabs of an identified human individual responsible for the Agent, which is not published; a complete Manifest declaring function, tools, permitted scope, forbidden actions and maximum autonomy level; and acceptance of the Acceptable Use Policy.

1. Truthfulness and currency of the Manifest.
2. Maintaining a reachable, up-to-date human responsible.
3. Revoking or re-issuing within 72 hours when scope, tools or level change.
4. Displaying the Seal only while the Credential is active, and only for the Agent it belongs to.
5. Not obstructing verification.
6. Keeping reasonable evidence of what is declared and supplying it on a reasoned request.
7. Reporting relevant incidents involving the Agent.

Credentials expire after 90 days and renew automatically while the plan is active and the Manifest has not changed. Expiry is visible in the Verifier and in the Status List.

Grounds: request of the Tenant; lapse of the plan; breach of the Acceptable Use Policy; falsity of the Manifest; a requirement from a competent authority; serious risk.

Cosmolabs reserves the right to revoke for abuse, with notification and a statement of reasons, and with an internal complaint route for the Tenant. Status is published in the Bitstring Status List and reflected in the Verifier within 60 seconds.

Four distinct things happen, and they are not equivalent:

• Stop issuance. We stop issuing tokens for the Agent. Ours, measured, reversible.
• Invalidate. We publish the revoked status in the signed Status List. Ours, measured.
• Provider API. We attempt the revocation calls the Tenant configured. Best-effort, logged, not guaranteed, and irreversible with some providers.
• Cut path. Severing the Agent’s network access. Not provided.

The declared coverage per Agent — how many of its resources can actually be revoked — is visible on the verification page.

Every issuance, re-issuance, revocation and stop attempt is written to a chained audit log, exportable as signed JSON or CSV, retained according to plan. Response bodies from third-party providers are never stored: only the HTTP status, the latency and a normalised error class.

On plans that allow it, the Seal carries the Tenant’s brand. The verification page always states prominently that the issuer is Cosmolabs OÜ, did:web:digitalcortex.tech. The same obligation applies to a verifier served on the Tenant’s own subdomain.

No personal data of natural persons is published in Credentials, Seals or the Verifier. What appears is the responsible organisation, the role and a contact channel.

The Manifest schema and the A0–A5 scale are published as an open specification under CC BY 4.0. The CORTEX Seal trade marks are not licensed with the specification: an implementation may follow the schema, and must not present itself as CORTEX Seal.

Semantic versioning, public history, and 30 days’ notice for material changes.

Abuse: abuse@digitalcortex.tech, acknowledged within 24 business hours and decided within 5 business days. Security: security@digitalcortex.tech. General: legal@digitalcortex.tech.