mainsequence 6.0.52__tar.gz → 7.0.0__tar.gz

mainsequence-7.0.0/MANIFEST.in

@@ -0,0 +1 @@
+include tests/fixtures/time_index_table_update_hash_v2_golden.json

{mainsequence-6.0.52 → mainsequence-7.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 6.0.52
+Version: 7.0.0
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: LicenseRef-MainSequence-Proprietary
@@ -55,7 +55,7 @@ The Main Sequence Python SDK is the client and development toolkit for the Main
 
 The Main Sequence platform allows you to:
 
-1. rapidly build and deploy data products and data workflows as a unified API with normalized table contracts through `MetaTable`s and `DataNode`s
+1. rapidly build and deploy data products with normalized `MetaTable` contracts and `TimeIndexTableUpdater` producer workflows
 2. rapidly deploy RBAC-enabled dashboards on the platform
 3. rapidly deploy agents using the Google Agent SDK
 
@@ -69,6 +69,7 @@ The key idea is that you can focus on development and deployment, while the plat
 - Documentation: [Documentation Site](https://mainsequence-sdk.github.io/mainsequence-sdk/)
 - Security policy: [SECURITY.md](SECURITY.md)
 - Release history: [CHANGELOG.md](CHANGELOG.md)
+- Major-version migration: [6.x to 7.0 hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
 
 ## What this repository contains
 
@@ -76,8 +77,8 @@ This repository contains the SDK and the documentation used to build and operate
 
 Main package areas:
 
-- `mainsequence.meta_tables`: `MetaTable`s, `DataNode`s, update workflows, and persistence
-- `mainsequence.client`: API client models for projects, jobs, data node storages, sharing, and platform resources
+- `mainsequence.meta_tables`: `MetaTable`s, `TimeIndexTableUpdater`s, update workflows, and persistence
+- `mainsequence.client`: API client models for projects, jobs, time-index tables, sharing, and platform resources
 - `mainsequence.cli`: the `mainsequence` command-line interface
 
 Repository areas:
@@ -98,11 +99,13 @@ Recommended entry points:
 - Beginner tutorial:
   - [MainSequence SDK tutorial Project](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
 - Knowledge:
-  - [Data Nodes](docs/knowledge/data_nodes.md)
+  - [Time-Index Table Updaters](docs/knowledge/time_index_table_updates.md)
   - [MetaTables](docs/knowledge/meta_tables/index.md)
   - [Constants and Secrets](docs/knowledge/infrastructure/constants_and_secrets.md)
   - [Scheduling Jobs](docs/knowledge/infrastructure/scheduling_jobs.md)
   - [Streamlit Dashboards](docs/knowledge/dashboards/streamlit/index.md)
+- Migrations:
+  - [6.x to 7.0: Time-Index Table Updater hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
 - CLI:
   - [CLI Overview](docs/cli/index.md)
 
@@ -149,7 +152,7 @@ mainsequence project build_local_venv --path .
 From there, the normal learning path is:
 
 1. model your first canonical table with a backend-managed `MetaTable`
-2. create your first `DataNode` as an opinionated MetaTable-backed update workflow
+2. create your first `TimeIndexTableUpdater` as an opinionated MetaTable-backed update workflow
 3. understand sharing and RBAC for published tables
 4. add an API or another application surface
 5. schedule jobs

{mainsequence-6.0.52 → mainsequence-7.0.0}/README.md

@@ -13,7 +13,7 @@ The Main Sequence Python SDK is the client and development toolkit for the Main
 
 The Main Sequence platform allows you to:
 
-1. rapidly build and deploy data products and data workflows as a unified API with normalized table contracts through `MetaTable`s and `DataNode`s
+1. rapidly build and deploy data products with normalized `MetaTable` contracts and `TimeIndexTableUpdater` producer workflows
 2. rapidly deploy RBAC-enabled dashboards on the platform
 3. rapidly deploy agents using the Google Agent SDK
 
@@ -27,6 +27,7 @@ The key idea is that you can focus on development and deployment, while the plat
 - Documentation: [Documentation Site](https://mainsequence-sdk.github.io/mainsequence-sdk/)
 - Security policy: [SECURITY.md](SECURITY.md)
 - Release history: [CHANGELOG.md](CHANGELOG.md)
+- Major-version migration: [6.x to 7.0 hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
 
 ## What this repository contains
 
@@ -34,8 +35,8 @@ This repository contains the SDK and the documentation used to build and operate
 
 Main package areas:
 
-- `mainsequence.meta_tables`: `MetaTable`s, `DataNode`s, update workflows, and persistence
-- `mainsequence.client`: API client models for projects, jobs, data node storages, sharing, and platform resources
+- `mainsequence.meta_tables`: `MetaTable`s, `TimeIndexTableUpdater`s, update workflows, and persistence
+- `mainsequence.client`: API client models for projects, jobs, time-index tables, sharing, and platform resources
 - `mainsequence.cli`: the `mainsequence` command-line interface
 
 Repository areas:
@@ -56,11 +57,13 @@ Recommended entry points:
 - Beginner tutorial:
   - [MainSequence SDK tutorial Project](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
 - Knowledge:
-  - [Data Nodes](docs/knowledge/data_nodes.md)
+  - [Time-Index Table Updaters](docs/knowledge/time_index_table_updates.md)
   - [MetaTables](docs/knowledge/meta_tables/index.md)
   - [Constants and Secrets](docs/knowledge/infrastructure/constants_and_secrets.md)
   - [Scheduling Jobs](docs/knowledge/infrastructure/scheduling_jobs.md)
   - [Streamlit Dashboards](docs/knowledge/dashboards/streamlit/index.md)
+- Migrations:
+  - [6.x to 7.0: Time-Index Table Updater hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
 - CLI:
   - [CLI Overview](docs/cli/index.md)
 
@@ -107,7 +110,7 @@ mainsequence project build_local_venv --path .
 From there, the normal learning path is:
 
 1. model your first canonical table with a backend-managed `MetaTable`
-2. create your first `DataNode` as an opinionated MetaTable-backed update workflow
+2. create your first `TimeIndexTableUpdater` as an opinionated MetaTable-backed update workflow
 3. understand sharing and RBAC for published tables
 4. add an API or another application surface
 5. schedule jobs

{mainsequence-6.0.52 → mainsequence-7.0.0}/agent_scaffold/AGENTS.md

@@ -62,7 +62,7 @@ CLI/SDK operations, and validation steps.
 Core responsibilities:
 
 - translate user intent into the correct Main Sequence implementation path:
-  - for data publishing and data pipelines, use `DataNode`s and `MetaTable`s
+  - for data publishing and data pipelines, use `TimeIndexTableUpdater`s and `MetaTable`s
   - for APIs serving the Command Center frontend, use the contract-authoritative
     FastAPI release workflow
   - for visualization, confirm the delivery target with the user:
@@ -80,7 +80,7 @@ Core responsibilities:
 
 Typical outcomes include:
 
-- build a `DataNode` to publish a data pipeline
+- build a `TimeIndexTableUpdater` to publish a data pipeline
 - build a `MetaTable` to record operational or application data
 - build and release a `FastAPI` API whose Command Center contract-bearing
   responses conform to a recorded revision of the canonical Command Center SDK
@@ -140,7 +140,7 @@ Delegation rules:
 
 ## Main Sequence Source-Of-Truth Rule
 
-For any task involving Main Sequence code, CLI usage, DataNodes, orchestration, jobs, dashboards,
+For any task involving Main Sequence code, CLI usage, TimeIndexTableUpdaters, orchestration, jobs, dashboards,
 agents, releases, artifacts, RBAC, or platform
 validation, always consult the latest relevant Main Sequence documentation before acting.
 
@@ -198,8 +198,8 @@ Typical routing:
   `.agents/skills/mainsequence/project_to_agent/SKILL.md`
 - project status audits, blocker analysis, failure classification, and upstream SDK assessment:
   `.agents/skills/mainsequence/maintenance/bug_auditor/SKILL.md`
-- DataNodes, updates, identifiers, schema, metadata:
-  `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
+- TimeIndexTableUpdaters, updates, identifiers, schema, metadata:
+  `.agents/skills/mainsequence/data_publishing/time_index_table_updates/SKILL.md`
 - MetaTables, SQLAlchemy contracts, backend-managed registration, and governed operations:
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - platform data discovery, published table search, and object identification before implementation:

{mainsequence-6.0.52 → mainsequence-7.0.0}/agent_scaffold/skills/a2a_sdk_execution/SKILL.md

@@ -71,6 +71,9 @@ mainsequence agent session get_or_create \
 ```
 
 Use the returned session `uid` as the target `AgentSession` UID.
+The returned `runtime_capabilities` map is a read-only advertisement from the
+session harness. Inspect it when capability-aware behavior is required; never
+construct, send, or override it from client code.
 
 If this A2A request originates from an existing caller session, include the
 parent session UID:

{mainsequence-6.0.52 → mainsequence-7.0.0}/agent_scaffold/skills/application_surfaces/api_surfaces/SKILL.md

@@ -88,7 +88,7 @@ Record:
   administrative, webhook, external integration, or backend-to-backend
 - the exact contract ID and role for each request or response body
 - route paths, HTTP methods, authentication expectations, and error semantics
-- upstream `APIDataNode`, MetaTable, service, or external data dependencies
+- upstream `TimeIndexTableRef`, MetaTable, service, or external data dependencies
 - whether the API uses backend transport or a contract-defined direct
   development transport
 

{mainsequence-6.0.52 → mainsequence-7.0.0}/agent_scaffold/skills/data_access/exploration/SKILL.md

@@ -1,27 +1,27 @@
 ---
 name: mainsequence-data-exploration
-description: Use this skill when the task is to discover what `DataNode` or `MetaTable` data already exists on the Main Sequence platform before implementation starts.
+description: Use this skill when the task is to discover what `TimeIndexMetaTable` or `MetaTable` data already exists on the Main Sequence platform before implementation starts.
 ---
 
 # Main Sequence Data Exploration
 
 ## Overview
 
-Use this skill when the task is about discovering what `DataNode` or `MetaTable` data is already available on the platform before implementation starts.
+Use this skill when the task is about discovering what `TimeIndexMetaTable` or `MetaTable` data is already available on the platform before implementation starts.
 
 This skill is for discovery only.
 
 It helps answer questions such as:
 
 - what published data already exists on this platform
-- whether the right surface is a `DataNode` or `MetaTable`
+- whether the right storage surface is a `TimeIndexMetaTable` or `MetaTable`
 - which identifier, storage UID, or object UID should be used
 - what metadata is available for those objects
 - what still needs to be clarified before implementation starts
 
 ## This Skill Can Do
 
-- discover published `DataNode` tables through the CLI
+- discover published time-index tables through the CLI
 - inspect published table identifiers, storage UIDs, and metadata
 - search for tables by keyword, description, or column name
 - inspect organization-visible table identifiers
@@ -32,7 +32,7 @@ It helps answer questions such as:
 
 This skill must not claim ownership of:
 
-- producing or modifying `DataNode` pipelines
+- producing or modifying `TimeIndexTableUpdater` pipelines
 - designing `MetaTable` registration or operation behavior
 - deciding code-level read patterns for discovered datasets
 - building APIs or dashboards
@@ -45,8 +45,8 @@ This skill discovers and identifies data. It does not publish, redesign, or defi
 
 - project bootstrap, scaffolding, and routing:
   `.agents/skills/mainsequence/project_design/SKILL.md`
-- `DataNode` creation or modification:
-  `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
+- `TimeIndexTableUpdater` creation or modification:
+  `.agents/skills/mainsequence/data_publishing/time_index_table_updates/SKILL.md`
 - `MetaTable` registration or operation work:
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - FastAPI providers serving the Command Center frontend:
@@ -62,7 +62,7 @@ Streamlit dashboard implementation is app-owned project code, not a Main Sequenc
 
 1. `AGENTS.md`
 2. `docs/cli/index.md`
-3. `docs/knowledge/data_nodes.md`
+3. `docs/knowledge/time_index_table_updates.md`
 4. `docs/knowledge/meta_tables/index.md` when the exploration touches row-oriented storage
 
 ## Inputs This Skill Needs
@@ -79,7 +79,7 @@ Before exploring, collect or infer:
 
 For every non-trivial exploration task, decide:
 
-1. Is the data surface a `DataNode` or `MetaTable`?
+1. Is the storage surface a `TimeIndexMetaTable` or `MetaTable`?
 2. Do we know the identifier already, or do we need to search first?
 3. What metadata or object details are needed to complete the discovery?
 4. Which implementation skill should receive the handoff after discovery?
@@ -97,17 +97,17 @@ Discovery priority:
 - use column lookup only when the user is specifically searching for a schema or column name
 - use detail only after you have identified the candidate object you want to inspect
 
-Semantic description discovery for published DataNode storage searches
+Semantic description discovery for published time-index tables searches
 `TimeIndexMetaTable` metadata rows through:
 
 - `GET /api/v1/time-index-meta-tables/description-search/?q=<text>`
 
-This is the DataNode discovery surface because published DataNode storage is
+This is the time-index table discovery surface because published output tables are
 represented by `TimeIndexMetaTable` metadata.
 
 Typical semantic discovery commands:
 
-- `mainsequence data-node search "<keyword>"`
+- `mainsequence time-index-table search "<keyword>"`
 
 Optional ranking knobs for description discovery:
 
@@ -149,10 +149,10 @@ profile-to-table identity and must match the parent `TimeIndexMetaTable.uid`.
 Structured filtering is a different path. Use it only when you already know the
 field to filter by:
 
-- `mainsequence data-node list`
-- `mainsequence data-node list --show-filters`
-- `mainsequence data-node list --filter KEY=VALUE`
-- `mainsequence data-node detail <DATA_NODE_STORAGE_UID>`
+- `mainsequence time-index-table list`
+- `mainsequence time-index-table list --show-filters`
+- `mainsequence time-index-table list --filter KEY=VALUE`
+- `mainsequence time-index-table detail <TIME_INDEX_META_TABLE_UID>`
 
 Collection listing is scoped to one Organization Environment. Inside a
 registered project checkout, the CLI derives that scope from the process-frozen
@@ -163,15 +163,15 @@ context while unrelated local development remains available.
 Column lookup is also a different path. Use it only for schema-name discovery,
 not as the default dataset discovery flow:
 
-- `mainsequence data-node search "<column-name>" --mode column`
+- `mainsequence time-index-table search "<column-name>" --mode column`
 
 Raw SQL inspection is only for targeted exploration after you have a UID:
 
 - `mainsequence meta-table run_query <META_TABLE_UID> "SELECT * FROM public.some_table LIMIT 100"`
-- `mainsequence data-node run_query <DATA_NODE_STORAGE_UID> "SELECT * FROM public.some_table LIMIT 100"`
+- `mainsequence time-index-table run_query <TIME_INDEX_META_TABLE_UID> "SELECT * FROM public.some_table LIMIT 100"`
 
-Use the MetaTable command for `MetaTable` UIDs. Use the DataNode command only
-for `DataNode` storage UIDs. Do not confuse the two surfaces.
+Use the MetaTable command for `MetaTable` UIDs. Use the time-index-table command only
+for `TimeIndexMetaTable` UIDs. Do not confuse the two surfaces.
 
 For direct SDK/backend usage, MetaTable raw SQL is sent as a JSON string body,
 not as an object. Do not send `{ "sql": "SELECT ..." }`.
@@ -182,12 +182,12 @@ Use the CLI or SDK client to identify what exists and collect the relevant ident
 
 Do not define code-level read patterns here.
 
-For `DataNode` discovery specifically:
+For time-index table discovery specifically:
 
-- start with `mainsequence data-node search`
-- use `mainsequence data-node list` only when you need broader enumeration or structured filters
-- use `mainsequence data-node search "<column-name>" --mode column` only for schema-name lookup
-- use `mainsequence data-node detail` only after search or list identified the target storage
+- start with `mainsequence time-index-table search`
+- use `mainsequence time-index-table list` only when you need broader enumeration or structured filters
+- use `mainsequence time-index-table search "<column-name>" --mode column` only for schema-name lookup
+- use `mainsequence time-index-table detail` only after search or list identified the target storage
 
 ### 3. Report platform objects with evidence
 
@@ -205,7 +205,7 @@ Once the discovery is complete, hand off to the correct implementation skill.
 
 Examples:
 
-- if the task is about publishing or modifying time-series data, hand off to `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
+- if the task is about publishing or modifying time-series data, hand off to `.agents/skills/mainsequence/data_publishing/time_index_table_updates/SKILL.md`
 - if the task is about row-oriented operational data, hand off to `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - if the task is about APIs or dashboards, hand off to the relevant surface skill after discovery is complete
 
@@ -214,7 +214,7 @@ Examples:
 When reviewing an exploration result, look for:
 
 - a discovery claim without CLI evidence
-- confusion between `DataNode` and `MetaTable`
+- confusion between updater behavior, `TimeIndexMetaTable`, and `MetaTable`
 - jumping into implementation work before discovery is complete
 - claiming implementation conclusions from a discovery-only pass
 

{mainsequence-6.0.52 → mainsequence-7.0.0}/agent_scaffold/skills/data_publishing/meta_tables/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: mainsequence-meta-tables
-description: Use this skill when the task is about defining, querying, or reviewing Main Sequence MetaTables. This skill owns SQLAlchemy table contracts, backend-managed table authoring, external table registration, governed compiled SQL operations, foreign keys, indexes, naming, cadence, and validation rules. For Alembic migration lifecycle work, use the mainsequence-metatable-migrations skill. It does not own DataNode producers, API route contracts, scheduling, releases, or sharing policy.
+description: Use this skill when the task is about defining, querying, or reviewing Main Sequence MetaTables. This skill owns SQLAlchemy table contracts, backend-managed table authoring, external table registration, governed compiled SQL operations, foreign keys, indexes, naming, cadence, and validation rules. For Alembic migration lifecycle work, use the mainsequence-metatable-migrations skill. It does not own TimeIndexTableUpdater producers, API route contracts, scheduling, releases, or sharing policy.
 ---
 
 # Main Sequence MetaTables
 
 ## Overview
 
-Use this skill when the task changes row-oriented project tables that are not naturally time-series DataNodes.
+Use this skill when the task changes row-oriented project tables that are not naturally time-indexed.
 
 This skill is for schema-driven application tables registered through TS Manager as `MetaTable` resources.
 
@@ -21,13 +21,13 @@ This skill is for schema-driven application tables registered through TS Manager
 - design governed compiled SQL read and write operations
 - route provider-based Alembic contract evolution to the MetaTable migration skill
 - review table contracts for physical-name, namespace, and identifier issues
-- review whether a task should be a `MetaTable` or a `DataNode`
+- review whether a task should be a `MetaTable` or a `TimeIndexTableUpdater`
 
 ## This Skill Must Not Claim
 
 This skill must not claim ownership of:
 
-- DataNode producer contracts
+- TimeIndexTableUpdater producer contracts
 - Command Center FastAPI wire contracts
 - workspace payloads
 - job scheduling, image pinning, or releases
@@ -41,8 +41,8 @@ If the user is still in the discovery process and does not yet know what data ex
   `.agents/skills/mainsequence/data_access/exploration/SKILL.md`
 - MetaTable migrations:
   `.agents/skills/mainsequence/data_publishing/meta_table_migrations/SKILL.md`
-- DataNodes:
-  `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
+- TimeIndexTableUpdaters:
+  `.agents/skills/mainsequence/data_publishing/time_index_table_updates/SKILL.md`
 - Command Center-serving FastAPI providers:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
 - Jobs, images, resources, and releases:
@@ -84,7 +84,7 @@ If ownership of the physical table lifecycle is unclear, stop before choosing a
 
 For every non-trivial task, decide:
 
-1. Is this table really row-oriented, or should it be a DataNode?
+1. Is this table really row-oriented, or should it be a TimeIndexTableUpdater?
 2. What is the business key?
 3. Who owns the catalog boundary: `platform_managed` or `external_registered`?
 4. Who owns physical DDL: `backend_managed`, `alembic_managed`, or `external_registered`?
@@ -236,7 +236,7 @@ selected `AlembicMetaTableMigration.metatable_models` list and let
 and bind them.
 
 For platform-managed migration registration, the data source is resolved from
-the active Main Sequence project/session, the same way DataNode does. Do not
+the active Main Sequence project/session, the same way TimeIndexTableUpdater does. Do not
 require or thread a `data_source_uid` through normal platform-managed example
 code.
 
@@ -389,14 +389,14 @@ Only use physical table names returned by registered `MetaTable` objects when co
 
 Do not hardcode platform-managed physical names manually.
 
-### 7. DataNode storage deletes use the DataNode tail-delete API
+### 7. Updater output-table deletes use the time-index-table tail-delete API
 
-For `PlatformTimeIndexMetaTable` storage owned by DataNodes, do not design raw
+For `PlatformTimeIndexMetaTable` output tables populated by TimeIndexTableUpdaters, do not design raw
 SQL delete operations or compiled SQL delete operations for rollback, repair, or
-stream cleanup. Route that work to the DataNode skill and use
+stream cleanup. Route that work to the TimeIndexTableUpdater skill and use
 `TimeIndexMetaTable.delete_after_date(...)`.
 
-The DataNode delete path is:
+The TimeIndexTableUpdater delete path is:
 
 ```text
 POST /api/v1/time-index-meta-tables/<table_uid>/delete-after-date/
@@ -426,9 +426,9 @@ When reviewing an existing MetaTable workflow, look for:
 - migration work that asks users to define backend payloads, artifact rows, or SDK request objects
 - compiled SQL operations without complete table scope
 - raw SQL that hardcodes stale physical names
-- raw SQL or compiled SQL deletes against DataNode-owned
+- raw SQL or compiled SQL deletes against TimeIndexTableUpdater-owned
   `PlatformTimeIndexMetaTable` storage instead of `delete_after_date(...)`
-- a table that should really be modeled as a DataNode instead
+- a table that should really be modeled as a TimeIndexTableUpdater instead
 
 ## Validation Checklist