Architecture decisions

Decision records preserve the reasoning and status of SDK architecture changes. A Proposed record does not describe implemented behavior. Read each record for its status and any superseding decisions.

The implemented context change is ADR 0035, a partial successor to ADR 0031. The SDK ownership boundary is recorded in ADR 0034.

Records

• ADR 0002: Multidimensional DataNode Update Contract
• ADR 0016: DType Serialization and Parsing Contract
• ADR 0017: MetaTable Schema Graph Client API
• ADR 0018: Platform-Managed MetaTable Runtime Physical Binding
• ADR 0019: Class-Based MetaTable Foreign Keys
• ADR 0020: Alembic-Based MetaTable Migrations
• ADR 0021: Migration-First Platform-Managed MetaTables
• ADR 0022: Thin SDK Alembic-Owned MetaTable Migrations
• ADR 0023: Alembic-Owned Foreign Keys And Indexes
• ADR 0024: Typed Reserved MetaTable Collection Create
• ADR 0025: Platform Time-Index Unique Grain Index
• ADR 0026: SDK-Owned Migration Scaffolding And Helpers
• ADR 0027: Automatic DataNode Dependency Tree Self-Healing
• ADR 0028: MetaTable Storage Hash As Utility
• ADR 0029: A2A Message Send Only
• ADR 0030: Server-Owned Dynamic Platform Skill Catalog
• ADR 0031: Git-Native Process CodeRepositoryBranch Context
• ADR 0032: Read Backend Responses Tolerantly
• ADR 0033: Read Closed Value Sets Tolerantly
• ADR 0034: Extract the MetaTables Python API from mainsequence

• ADR 0035: Independent Git source and platform execution context

• ADR-0036: Request-scoped logged user

• 0036: Generic operation correlation in owner logs

• ADR 0037: The session lives in the operating system credential store

• ADR 0038: Project MCP on FastAPI releases

• ADR 0039: Application skills through the MCP Skills extension

• ADR 0040: Caller context on release requests, SDK calls and Job runs

• ADR 0041: Cold-start-aware calls between releases