forgecode

Identity

Names: dev.forgecode; short alias forgecode.
Native format: forgecode-sqlite, conversation context.messages snapshots.
Session ID: conversations.conversation_id. The supplied source evidence does not establish a namespace; uniqueness across independent stores needs qualification before colliding records are merged.
Notes: Native reasoning types establish full/summary/encrypted visibility and signatures. Text/AI/Image/Empty outputs retain their native values; URL/data-URL images are not fetched. Attached assistant usage is per response and supports a derived inference. Actual counters normalize; Approx counts stay metadata. USD is recorded, but cost source/billing remain unknown. Current tools, metrics and workspace ID are tail state, not causal file events.

Position basis

Record family	Position basis	Commit boundary
transcript	context.messages-array-index	transaction
current-state	snapshot	transaction

Use only positions established by the stated format and mapping evidence. Current-state rows without transcript positions go at the end, as the snapshot tail. A protocol commit boundary takes precedence over physical EOF; uncommitted bytes are not a gap.

Destinations

forgecode: native facts without a standard field

Fact	Native name	Destination
Remaining source facts	The native row or item used for this projection	`native.record` on the record for this source value, or `native.blob` for a blob containing the entire source value. Preserve native JSON text columns as strings. Use a separate vendor record when several source rows feed one projection. ASR-035 applies to unsafe numbers.
Unpaired result identity	The result’s native call-ID field named above	`tool_result.nativeCallId`, verbatim
Call details	Native tool call	`tool_call` `_meta` `dev.forgecode/call`
Accounting, including estimates	Attached usage object	`inference` `_meta` `dev.forgecode/usage`
Current state	Conversation row, context without messages, metrics and workspace fields	`session_info` `_meta` `dev.forgecode/state`, object preserving those named native members
Database schema	`sqlite_schema` rows	manifest `_meta` `dev.forgecode/unassigned`, using the common shape.

Usage

Select one report per native accounting identity only when this entry establishes that identity. Keep unjoinable or overlapping reports as native evidence. Declare incomplete semantic coverage. Schema defaults and placeholder zeros are not reported usage. Backend inclusion rules require evidence; do not infer them from a model name.

Lane and unassigned facts

Facts without established session ownership use manifest _meta["dev.forgecode/unassigned"] with the common shape. Selection may retain these facts with any session subset, including an empty subset, but must not imply session ownership. State the selection policy in the export report.

Losses

Declare every applicable loss under ASR-157. Missing model rendering, accounting joins, lineage or exact context boundaries remain losses when this entry does not qualify them. Unknown ownership is not itself lost data. Omitted unassigned facts use a documented vendor loss or report, not a new core category.

Evidence

Basis: source-verified at ForgeCode commit 6ed5d37b6b45a2b6220877fd9aec5ba4c4b7f3c0 (forge_domain context/message/reasoning/tool-result types). Existing SQLite fixture has no producer receipt; current/legacy semantic tests are authored. No release version is qualified. Evidence applies only to the named formats and explicit mappings above. A real capture covers only exercised behavior. A no-model writer probe covers persistence, not model or tool execution. Authored tests do not qualify an agent version. Unlisted formats and link mappings remain unqualified.

Observations from 2026-10-27

observed, version 2.14.0: ForgeCode 2.14.0 retained edit, review and child sessions. Its compact command succeeded and resume worked, but the mutable store retained no projectable compaction boundary. Preserve the snapshot and declare the applicable loss. A successful command does not justify a compaction record. The ctx conversion produced 3 streams and 74 records, with 0 errors, 3 notices, 0 gaps and 0 unidentified inputs under validator-v0.1.2. These counts describe the selected output; an empty bundle qualifies no source format. No sanitized native fixture was retained for this observation. Whole native records use native.record or native.blob, with JSON text columns preserved as strings. The exporter’s own bookkeeping for serialization, partitioning and message keys belongs in the exporter namespace (rs.ctx for ctx), not in a provider metadata destination. These runs add no evidence for unexercised approvals, lineage links, compaction boundaries or exact request context.

{
  "name": "dev.forgecode",
  "aliases": [
    "forgecode"
  ],
  "namespace": {
    "rule": "none"
  },
  "positions": [
    {
      "family": "transcript",
      "basis": "context.messages-array-index",
      "boundary": "transaction"
    },
    {
      "family": "current-state",
      "basis": "snapshot",
      "boundary": "transaction"
    }
  ],
  "formats": [
    {
      "id": "forgecode-sqlite",
      "evidence": [
        0,
        2
      ]
    }
  ],
  "evidence": [
    {
      "label": "source",
      "revision": "6ed5d37b6b45a2b6220877fd9aec5ba4c4b7f3c0",
      "scope": "format-and-explicit-mappings"
    },
    {
      "label": "authored",
      "scope": "converter-tests-only"
    },
    {
      "label": "observed",
      "version": "2.14.0",
      "date": "2026-10-27",
      "scope": "SQLite context snapshots in .forge/.forge.db; Edit, review with child, native compact command and resume; 3 streams.",
      "limitations": "ForgeCode 2.14.0 retained edit, review and child sessions. Its compact command succeeded and resume worked, but the mutable store retained no projectable compaction boundary. Preserve the snapshot and declare the applicable loss. A successful command does not justify a compaction record.",
      "validation": {
        "streams": 3,
        "records": 74,
        "errors": 0,
        "notices": 3,
        "gaps": 0,
        "unidentifiedSources": 0
      },
      "validator": "validator-v0.1.2",
      "converter": "ctx-asr-authentic-captures-4"
    }
  ],
  "destinations": {
    "call": {
      "schema": {},
      "evidence": [
        0
      ]
    },
    "state": {
      "schema": {
        "type": "object"
      },
      "evidence": [
        0
      ]
    },
    "usage": {
      "schema": {
        "type": "object"
      },
      "evidence": [
        0
      ]
    }
  },
  "mappings": [
    {
      "native": "complete native row or event",
      "destination": "native.record or native.blob",
      "scope": "SQLite context snapshots in .forge/.forge.db",
      "evidence": [
        2
      ]
    }
  ]
}

Introduction

Format

Records

Trust

Extending and conforming

Agent registry

forgecode

forgecode

Identity

Position basis

Destinations

forgecode: native facts without a standard field

Links

Usage

Lane and unassigned facts

Losses

Evidence

Observations from 2026-10-27

​forgecode

​Identity

​Position basis

​Destinations

​forgecode: native facts without a standard field

​Links

​Usage

​Lane and unassigned facts

​Losses

​Evidence

​Observations from 2026-10-27

forgecode

Identity

Position basis

Destinations

forgecode: native facts without a standard field

Links

Usage

Lane and unassigned facts

Losses

Evidence

Observations from 2026-10-27