Skip to main content
Create and maintain Forge-owned typed records.
People can declare immutable record collections in Console. API and MCP clients can list and read those collections and create, update or remove records under current Knowledge permissions. Existing synchronized record responses keep their sourceId; authored records use collectionId and a positive numeric version.
Security: the bridge audit write is retired, and a CI gate keeps actors honest.
  • auditEvents.logBridgeEvent is removed. It let a caller with platform:manage write an audit event with any category, event and timestamp, and nothing had called it since the Bridge was removed.
  • A new Trust Fabric CI gate refuses a public function that stores, audits or passes on an actor its caller names (createdBy, uploadedBy, grantedBy, actor, authorId, subject and similar, including inside a list such as a sandbox command’s addedBy). The function records its authenticated caller instead.
  • A tool’s sandbox commands record who added them: a command already stored keeps its adder and time, and a new one names the person who saved it. An addedBy or addedAt sent with the command is ignored. The tool page names the adder, and listTools returns the names as sandboxCommandAdders.
  • A skill review set through skillDefinitions.update or updateSkill records the caller as its reviewer, now; a quality.reviewedBy or reviewedAt sent with the patch is ignored.
  • The skill detail page names who created a skill, and never shows their user id. listSkills returns the name as createdByName.
Security: a function records its caller as the actor.
Some public functions stored the actor their caller named instead of the caller: the uploader of a workflow document, the creator of a tool, skill, agent or step (including the createTool, createSkill, createWorkspaceSkill and createStep doors), the author of a scheduled org change, the actor of a bridge audit event, and who granted or revoked a worker’s raw-bash grant. A caller could name someone else. For a tool with no later governance edit, Forge treats the creator as the tool’s declaration editor, so a forged creator also hid the real author from the tool’s holds: their approval was not recorded as releasing their own work, and was not refused where an independent approver is required. Each of these now records the authenticated caller. The argument is still accepted, so existing callers keep working, and it is ignored. See Audit events.