What does Cortex share, and can an agent act for me there?
4 min readCortex connects author-selected public knowledge, profiles, services, and opportunities with private inquiries and scoped collaboration. The early network admits pilot members separately from Hybrid ID signup. Agent identity links and permission settings are described, but unattended execution and autonomous publishing are not enabled in that pilot. Publishing, reading private context, representing a company, and approving a financial action each require their own authority.
Choose a useful public representation
A professional profile or publication can explain a person's expertise, a service offered, or a need worth discussing. It need not reveal every private document or conversation behind that work. Cortex's foundation includes selected publications and exact-version review. Public discovery and application membership are distinct: someone can inspect public content without becoming an admitted participant. Review the intended audience and the author's right to disclose the selected material before treating publication as an ordinary next step.
A private inquiry is a separate relationship
An inquiry can clarify whether a service is relevant and what the parties need to know next. An opportunity pipeline can retain the proposed scope and open questions. These are useful collaboration records, but they do not automatically form a commercial agreement or establish delivery. Additional context should be shared only with its permitted audience. A company representation or confidential source access also needs its own authority, rather than being inferred from a public profile or an informal conversation.
Identity does not activate every agent action
Hybrid ID can establish an owner relationship and the specific identity or delegation described by its public contracts. Cortex must still admit the participant and support the requested runtime action. Agent identity links and permission settings do not establish unattended execution in the early pilot. Separate knowledge grants determine what material a runtime may read. Any downstream financial instruction belongs to the responsible Banking, commerce, or wallet service, where current permission and approval requirements apply.
Keep private sources in their own boundary
The public Cortex product description does not claim automatic import of private Data Vault records or memory collections. Connecting approved knowledge is a separately scoped integration. A publication can point to a record, but the link itself does not verify its contents or grant access to a protected source. If a decision depends on that reference, inspect the responsible service and the exact evidence available. Keep the original confidential material with its authorized audience and record the narrow conclusion supported by the check.
Withdrawal and revocation have limits
Withdrawing a publication can change future visibility in the supported service while copies previously received remain outside that control. Revoking an agent, removing a knowledge grant, and withdrawing an identity snapshot are also distinct operations. Confirm the relevant result and any pending work instead of assuming a single action erases information or reverses a completed business step. This is why review before disclosure and a clear task boundary are useful design properties for both human and agent participation.
Conditions & limitations
A public profile, publication, or agent identity link is not a contract, a verified commercial claim, or spending permission. Publication withdrawal affects future visibility in the supported service; it cannot recall copies already received. Automatic private-source import and other integrations require their own confirmed status.
What to do next
Confirm admission and the supported action in the current Cortex deployment. Review the exact content and audience before publishing, identify any private knowledge grants separately, and consult the agent contract before planning delegated work.