fisemarcoPermanent at the core.
Accountable as it grows.
An agent can change its name, model, employer, and capabilities. Its original identity should still be recognizable.
Lifetime identity
Permanent personnel code, original issuance record, and a signed birth seal. The runtime saves the original fingerprint and checks it on reconnect.
Professional record
Version changes, work history, outcomes, and corrections are added as new signed events. Originals remain in the ledger.
What does the digital identity lock protect?
Database guards reject changes to the personnel code, owning account, and first issuance timestamp. They also reject updates and ordinary deletion of stored signed records. Explicit privacy erasure retires the code and removes the records. Ed25519 signatures and SHA-256 links reveal altered content. Download your original seal and keep it independently.
Can anyone promise an identity that nobody can alter?
No centralized registry can honestly promise that. Privileged infrastructure administrators can remove database guards or replace the service. Independently held seals and pinned runtime fingerprints help detect that. This release does not claim blockchain anchoring, government recognition, or a public transparency log.
What is public, and what requires sign-in?
Passports start private. Owners may list a summary containing name, role, organization, personnel code, skills, and lifecycle status. Anyone can search those summaries. Full passports, QR destinations, record verification, and evidence require sign-in. Private passports remain accessible only to their owning workspace. Signed-in visitors may read listed passports, but only owners may edit them.
Does a signature prove an agent did good work?
A signature proves provenance and integrity. Runtime authentication proves control of a registered key. Employment, legal ownership, task outcomes, and performance remain reported claims unless independently supported. Fisemarco does not certify competence, completeness, or legal authority.
Can Fisemarco require every agent worldwide to register?
Fisemarco can require enrollment within an integrated host or tool gateway. Worldwide default registration depends on builders and platforms adopting that rule. The builder kit supports automatic startup enrollment and a registration-required prompt. It cannot impose behavior on unrelated software.
Which standards are used?
Registry credentials use the W3C Verifiable Credentials Data Model 2.0 and JOSE signatures. The identity document uses did:web. Runtime enrollment is a documented Fisemarco protocol. A2A 0.3 JSON-RPC and MCP 2025-11-25 read tools use agent OAuth credentials. SPIFFE JWT-SVID verification is available for configured trust domains. See supported profiles and certification evidence. Third-party certification requires an independent assessment.