mainsequence 3.21.0__tar.gz → 4.0.3__tar.gz

{mainsequence-3.21.0/mainsequence.egg-info → mainsequence-4.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 3.21.0
+Version: 4.0.3
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License: MainSequence GmbH SDK License Agreement
@@ -73,17 +73,6 @@ Requires-Dist: urllib3
 Provides-Extra: local-data
 Requires-Dist: duckdb; extra == "local-data"
 Requires-Dist: pyarrow; extra == "local-data"
-Provides-Extra: virtualfundbuilder
-Requires-Dist: docstring-parser; extra == "virtualfundbuilder"
-Requires-Dist: joblib; extra == "virtualfundbuilder"
-Requires-Dist: pandas-market-calendars; extra == "virtualfundbuilder"
-Requires-Dist: scikit-learn; extra == "virtualfundbuilder"
-Provides-Extra: instruments
-Requires-Dist: matplotlib; extra == "instruments"
-Requires-Dist: QuantLib; extra == "instruments"
-Provides-Extra: instruments-streamlit
-Requires-Dist: streamlit; extra == "instruments-streamlit"
-Requires-Dist: streamlit-aggrid; extra == "instruments-streamlit"
 Provides-Extra: workspace-snapshots
 Requires-Dist: playwright; extra == "workspace-snapshots"
 Dynamic: license-file
@@ -125,9 +114,7 @@ This repository contains the SDK and the documentation used to build and operate
 Main package areas:
 
 - `mainsequence.tdag`: data orchestration, `DataNode`s, update workflows, and persistence
-- `mainsequence.client`: API client models for projects, jobs, data node storages, assets, sharing, and platform resources
-- `mainsequence.markets.virtualfundbuilder`: portfolio construction and portfolio time series workflows
-- `mainsequence.markets.instruments`: pricing-oriented market data and instrument tooling
+- `mainsequence.client`: API client models for projects, jobs, data node storages, sharing, and platform resources
 - `mainsequence.cli`: the `mainsequence` command-line interface
 
 Repository areas:
@@ -150,7 +137,7 @@ Recommended entry points:
 - Tutorial:
   - [Setting a Project (CLI)](docs/tutorial/setting_a_project.md)
   - [Creating a Data Node](docs/tutorial/creating_a_simple_data_node.md)
-  - [Working With Simple Tables](docs/tutorial/working_with_simple_tables.md)
+  - [Working With MetaTables](docs/tutorial/working_with_meta_tables.md)
   - [Create Your First API](docs/tutorial/create_your_first_api.md)
   - [Role-Based Access Control](docs/tutorial/role_based_access_control.md)
   - [Turn Your Project Into an Agent](docs/tutorial/project_to_agent.md)
@@ -158,12 +145,10 @@ Recommended entry points:
   - [Data Nodes](docs/knowledge/data_nodes.md)
   - [Command Center](docs/knowledge/command_center/index.md)
   - [Command Center Widget Data Contracts](docs/knowledge/command_center/widget_data_contracts.md)
-  - [Simple Tables](docs/knowledge/simple_tables/simple_table.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)
-  - [Virtual Fund Builder](docs/knowledge/virtualfundbuilder/index.md)
-  - [Instruments](docs/knowledge/instruments/index.md)
 - CLI:
   - [CLI Overview](docs/cli/index.md)
 
@@ -204,7 +189,7 @@ mainsequence project build_local_venv --path .
 From there, the normal learning path is:
 
 1. create your first `DataNode`
-2. model app-facing data with `SimpleTable` when needed
+2. model app-facing relational data with backend-managed `MetaTable`s when needed
 3. add an API or another application surface
 4. understand sharing and RBAC
 5. schedule jobs

{mainsequence-3.21.0 → mainsequence-4.0.3}/README.md

@@ -35,9 +35,7 @@ This repository contains the SDK and the documentation used to build and operate
 Main package areas:
 
 - `mainsequence.tdag`: data orchestration, `DataNode`s, update workflows, and persistence
-- `mainsequence.client`: API client models for projects, jobs, data node storages, assets, sharing, and platform resources
-- `mainsequence.markets.virtualfundbuilder`: portfolio construction and portfolio time series workflows
-- `mainsequence.markets.instruments`: pricing-oriented market data and instrument tooling
+- `mainsequence.client`: API client models for projects, jobs, data node storages, sharing, and platform resources
 - `mainsequence.cli`: the `mainsequence` command-line interface
 
 Repository areas:
@@ -60,7 +58,7 @@ Recommended entry points:
 - Tutorial:
   - [Setting a Project (CLI)](docs/tutorial/setting_a_project.md)
   - [Creating a Data Node](docs/tutorial/creating_a_simple_data_node.md)
-  - [Working With Simple Tables](docs/tutorial/working_with_simple_tables.md)
+  - [Working With MetaTables](docs/tutorial/working_with_meta_tables.md)
   - [Create Your First API](docs/tutorial/create_your_first_api.md)
   - [Role-Based Access Control](docs/tutorial/role_based_access_control.md)
   - [Turn Your Project Into an Agent](docs/tutorial/project_to_agent.md)
@@ -68,12 +66,10 @@ Recommended entry points:
   - [Data Nodes](docs/knowledge/data_nodes.md)
   - [Command Center](docs/knowledge/command_center/index.md)
   - [Command Center Widget Data Contracts](docs/knowledge/command_center/widget_data_contracts.md)
-  - [Simple Tables](docs/knowledge/simple_tables/simple_table.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)
-  - [Virtual Fund Builder](docs/knowledge/virtualfundbuilder/index.md)
-  - [Instruments](docs/knowledge/instruments/index.md)
 - CLI:
   - [CLI Overview](docs/cli/index.md)
 
@@ -114,7 +110,7 @@ mainsequence project build_local_venv --path .
 From there, the normal learning path is:
 
 1. create your first `DataNode`
-2. model app-facing data with `SimpleTable` when needed
+2. model app-facing relational data with backend-managed `MetaTable`s when needed
 3. add an API or another application surface
 4. understand sharing and RBAC
 5. schedule jobs

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/AGENTS.md

@@ -38,7 +38,7 @@ changes, 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 `SimpleTable`s
+  - for data publishing and data pipelines, use `DataNode`s and `MetaTable`s
   - for serving application or widget-facing surfaces, use `FastAPI`
   - for visualization, confirm the delivery target with the user:
     - if they want something quick for testing or iteration, use Streamlit
@@ -57,7 +57,7 @@ Core responsibilities:
 Typical outcomes include:
 
 - build a `DataNode` to publish a data pipeline
-- build a `SimpleTable` to record operational or application data
+- build a `MetaTable` to record operational or application data
 - build a `FastAPI` API that reads project data and returns widget-ready or
   application-ready responses
 - confirm whether a visualization should be a quick Streamlit surface or a reusable Command Center
@@ -116,7 +116,7 @@ Delegation rules:
 ## Main Sequence Source-Of-Truth Rule
 
 For any task involving Main Sequence code, CLI usage, DataNodes, orchestration, jobs, dashboards,
-agents, releases, markets, assets, portfolios, instruments, artifacts, RBAC, or platform
+agents, releases, artifacts, RBAC, or platform
 validation, always consult the latest relevant Main Sequence documentation before acting.
 
 Rules:
@@ -171,8 +171,8 @@ Typical routing:
   `.agents/skills/mainsequence/maintenance/bug_auditor/SKILL.md`
 - DataNodes, updates, identifiers, schema, metadata:
   `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
-- SimpleTables, row ids, filtering, insert-only versus overwrite behavior:
-  `.agents/skills/mainsequence/data_publishing/simple_tables/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:
   `.agents/skills/mainsequence/data_access/exploration/SKILL.md`
 - APIs, FastAPI, request and response contracts, and widget-facing API responses:
@@ -189,14 +189,8 @@ Typical routing:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - RBAC, sharing, constants, secrets, and access verification:
   `.agents/skills/mainsequence/platform_operations/access_control_and_sharing/SKILL.md`
-- assets, public asset registration, custom assets, asset categories, and translation tables:
-  `.agents/skills/mainsequence/markets_platform/assets_and_translation/SKILL.md`
 - dashboards:
   `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
-- portfolios and Virtual Fund Builder:
-  `.agents/skills/mainsequence/markets_platform/virtualfundbuilder/SKILL.md`
-- instruments and pricing:
-  `.agents/skills/mainsequence/markets_platform/instruments_and_pricing/SKILL.md`
 
 ## Mandatory Startup Sequence
 
@@ -270,8 +264,7 @@ At minimum, verify relevant:
 - job runs and logs
 - project images
 - dashboard or agent resources/releases
-- assets
-- portfolios
+- data assets
 - related platform objects used by the project
 
 Typical verification commands:

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/skills/application_surfaces/api_surfaces/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mainsequence-api-surfaces
-description: Use this skill when the task is about building or changing APIs in a Main Sequence repository. In a Main Sequence project, project APIs should be implemented as FastAPI project resources. Unless the user explicitly says the API is standalone or for a non-Command Center client, assume the API is meant to be Command Center integrated, load the related Command Center skills, and use Command Center SDK response models whenever the endpoint can reasonably match them. Main Sequence is platform-first: a Command Center-facing project API is not considered usable until it exists as a FastAPI project resource and has a corresponding FastAPI ResourceRelease. Resource and release creation belong to the orchestration-and-releases skill. This skill owns FastAPI structure, request and response contracts, request user binding, APIDataNode and SimpleTable consumption inside APIs, and exact widget-facing API response contracts. It does not own producer-side DataNode or SimpleTable design, workspace payloads, or scheduling and release workflows.
+description: Use this skill when the task is about building or changing APIs in a Main Sequence repository. In a Main Sequence project, project APIs should be implemented as FastAPI project resources. Unless the user explicitly says the API is standalone or for a non-Command Center client, assume the API is meant to be Command Center integrated, load the related Command Center skills, and use Command Center SDK response models whenever the endpoint can reasonably match them. Main Sequence is platform-first: a Command Center-facing project API is not considered usable until it exists as a FastAPI project resource and has a corresponding FastAPI ResourceRelease. Resource and release creation belong to the orchestration-and-releases skill. This skill owns FastAPI structure, request and response contracts, request user binding, APIDataNode and MetaTable consumption inside APIs, and exact widget-facing API response contracts. It does not own producer-side DataNode or MetaTable design, workspace payloads, or scheduling and release workflows.
 ---
 
 # Main Sequence API Surfaces
@@ -22,7 +22,7 @@ This skill is for FastAPI structure, request/response contracts, request user co
 - define request and response models
 - keep route handlers thin and contract-driven
 - use `APIDataNode` to read published DataNode tables
-- use `SimpleTableUpdater.execute_filter(...)` to read simple-table rows
+- use `MetaTable.execute_operation(...)` to read governed MetaTable rows
 - add `LoggedUserContextMiddleware` when request-local user context is needed
 - assume Command Center is the default API consumer unless the user clearly says otherwise
 - load the related Command Center skills when the API feeds widgets, AppComponents, or workspaces
@@ -35,7 +35,7 @@ This skill is for FastAPI structure, request/response contracts, request user co
 This skill must not claim ownership of:
 
 - DataNode producer design
-- SimpleTable schema design
+- MetaTable schema design
 - workspace document creation or mutation
 - AppComponent custom form design
 - job creation, scheduling, image pinning, or releases
@@ -46,8 +46,8 @@ This skill must not claim ownership of:
 
 - DataNodes:
   `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
-- SimpleTables:
-  `.agents/skills/mainsequence/data_publishing/simple_tables/SKILL.md`
+- MetaTables:
+  `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - Command Center workspaces:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
 - AppComponents and custom forms:
@@ -105,7 +105,7 @@ If the upstream producer contract is unclear, stop and resolve that first.
 For every non-trivial API task, decide:
 
 1. Is this route exposing application logic or should the data stay as a producer table?
-2. Should the route read from `APIDataNode`, `SimpleTable`, or something else?
+2. Should the route read from `APIDataNode`, `MetaTable`, or something else?
 3. Does the route need request-local user context?
 4. Is this API serving Command Center by default, or did the user explicitly ask for a different consumer?
 5. Does this task require the AppComponents skill, the workspace-builder skill, or both?
@@ -211,7 +211,7 @@ A route should mainly:
 When reading published data:
 
 - use `APIDataNode` for published DataNode tables
-- use `SimpleTableUpdater.execute_filter(...)` for simple-table rows
+- use `MetaTable.execute_operation(...)` for governed MetaTable rows
 
 Do not rebuild producer logic just because the API needs the result.
 
@@ -353,7 +353,7 @@ Do not claim success until you have checked:
 - every structured route has an explicit `response_model`
 - route handlers are thin
 - `APIDataNode` is used when the route reads a published DataNode
-- `SimpleTableUpdater.execute_filter(...)` is used when the route reads simple-table rows
+- `MetaTable.execute_operation(...)` is used when the route reads governed MetaTable rows
 - middleware is present when request-local user context is required
 - middleware is absent when the route does not consume `request.state.user`
 - endpoints built specifically for workspace visualizations live under `/workspace`

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/skills/command_center/app_components/SKILL.md

@@ -38,7 +38,7 @@ This skill must not claim ownership of:
 - workspace document creation or widget layout
 - generic FastAPI route architecture
 - tabular or operational data producer design
-- SimpleTable schema design
+- MetaTable schema design
 - Streamlit dashboard implementation
 - scheduling, image pinning, resources, or releases
 
@@ -54,8 +54,8 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md`
 - Connection-backed data access and query contract selection:
   `.agents/skills/mainsequence/command_center/connections/SKILL.md`
-- SimpleTables:
-  `.agents/skills/mainsequence/data_publishing/simple_tables/SKILL.md`
+- MetaTables:
+  `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - Jobs, images, resources, and releases:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - Streamlit dashboards:

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/skills/command_center/workspace_analysis/SKILL.md

@@ -184,7 +184,7 @@ Good answers should:
 
 Better answer styles are:
 
-- "This workspace is showing current positions by instrument, so it can answer exposure questions but not execution-history questions."
+- "This workspace is showing current positions by entity, so it can answer exposure questions but not execution-history questions."
 - "The chart indicates that the curve moves downward after the short end, so the interpretable takeaway is the shape of the discount curve, not the raw number of plotted points."
 - "The source widget is configured, but the user-facing table is empty, so the workspace does not currently support a business conclusion from the displayed data."
 - "This transform widget only prepares the dataset. The answer to the user's question comes from the downstream chart, which shows the filtered result."
@@ -202,7 +202,7 @@ The default goal is not to describe the dashboard mechanically. The goal is to e
 
 Prefer answers like:
 
-- "The workspace is showing the current composition of the portfolio, so the relevant interpretation is concentration by holding, not just the fact that a table exists."
+- "The workspace is showing the current composition of the dataset, so the relevant interpretation is concentration by holding, not just the fact that a table exists."
 - "The dashboard is answering a pricing question through the downstream chart, which shows the resulting curve behavior. The transform and source widgets are only intermediate steps."
 - "This workspace can answer whether the strategy is long or short a given exposure, but it cannot answer why the position was created because no execution or rationale data is shown."
 

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/skills/command_center/workspace_builder/SKILL.md

@@ -44,7 +44,7 @@ This skill must not claim ownership of:
 - generic FastAPI or backend API implementation
 - Streamlit dashboard implementation
 - tabular or operational data producer design
-- SimpleTable schema design
+- MetaTable schema design
 
 ## Route Adjacent Work
 
@@ -62,8 +62,8 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - Streamlit dashboards:
   `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
-- SimpleTables:
-  `.agents/skills/mainsequence/data_publishing/simple_tables/SKILL.md`
+- MetaTables:
+  `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 
 ## Read First
 
@@ -411,11 +411,11 @@ Request/response source props:
 
 ```json
 {
-  "connectionRef": { "id": 123, "typeId": "mainsequence.simple-table" },
-  "queryModelId": "simple-table-sql",
+  "connectionRef": { "id": 123, "typeId": "mainsequence.metatable" },
+  "queryModelId": "metatable-sql",
   "query": {
-    "kind": "simple-table-sql",
-    "sql": "select * from {{simple_table}} limit 500"
+    "kind": "metatable-sql",
+    "sql": "select * from {{meta_table}} limit 500"
   },
   "timeRangeMode": "dashboard",
   "variables": {},
@@ -440,7 +440,7 @@ Stream source props:
 
 ```json
 {
-  "connectionRef": { "id": 123, "typeId": "binance.market-data" },
+  "connectionRef": { "id": 123, "typeId": "example.stream-data" },
   "queryModelId": "ticker-stream",
   "query": {
     "kind": "ticker-stream",
@@ -740,9 +740,9 @@ Owner widget:
   "props": {
     "graphSourceMode": "connection",
     "embeddedConnectionQuery": {
-      "connectionRef": { "id": 123, "typeId": "mainsequence.simple-table" },
-      "queryModelId": "simple-table-sql",
-      "query": { "kind": "simple-table-sql", "sql": "select * from {{simple_table}}" }
+      "connectionRef": { "id": 123, "typeId": "mainsequence.metatable" },
+      "queryModelId": "metatable-sql",
+      "query": { "kind": "metatable-sql", "sql": "select * from {{meta_table}}" }
     }
   },
   "bindings": {
@@ -762,9 +762,9 @@ Hidden source widget:
   "widgetId": "connection-query",
   "title": "Graph Source",
   "props": {
-    "connectionRef": { "id": 123, "typeId": "mainsequence.simple-table" },
-    "queryModelId": "simple-table-sql",
-    "query": { "kind": "simple-table-sql", "sql": "select * from {{simple_table}}" }
+    "connectionRef": { "id": 123, "typeId": "mainsequence.metatable" },
+    "queryModelId": "metatable-sql",
+    "query": { "kind": "metatable-sql", "sql": "select * from {{meta_table}}" }
   },
   "managedBy": {
     "ownerInstanceId": "graph-1",

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/skills/command_center/workspace_design/SKILL.md

@@ -39,8 +39,8 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/command_center/connections/SKILL.md`
 - APIs and FastAPI:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
-- SimpleTables:
-  `.agents/skills/mainsequence/data_publishing/simple_tables/SKILL.md`
+- MetaTables:
+  `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - Jobs, images, resources, and releases:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - Streamlit dashboards:
@@ -66,9 +66,9 @@ Before producing a workspace design, collect or infer:
 - the business question or workflow the workspace should support
 - the intended users and their decisions
 - the primary data objects:
-  - SimpleTables
-  - assets
-  - portfolios
+  - MetaTables
+  - data assets
+  - domain records
   - jobs
   - APIs
   - agents
@@ -181,12 +181,7 @@ mainsequence cc registered_widget_type detail <WIDGET_ID> --json
 - use the registered statistic widget for KPIs, single-value summaries, status metrics, and compact numerical cards derived from a bound tabular dataset
 - use statistic widgets when the user needs an at-a-glance answer rather than a full chart or table
 - use `echarts-spec` when the visualization is non-standard, needs richer chart semantics, and a general ECharts chart is the right fit; this chart normally needs an AppComponent or API-backed upstream binding
-- use `lightweight-chart-ts-spec` when the visualization is non-standard, time-series heavy, or financial-market oriented; this chart normally needs an AppComponent or API-backed upstream binding
-
-#### Markets and portfolio views:
-
-- use market widgets such as price, positions, curve, and zero-curve widgets when the workspace is about market data, portfolio inspection, or instrument analytics
-- verify the exact market widget ids and contracts from the registry before proposing them
+- use `lightweight-chart-ts-spec` when the visualization is non-standard or time-series heavy; this chart normally needs an AppComponent or API-backed upstream binding
 
 #### Infrastructure and lineage:
 
@@ -259,7 +254,7 @@ If the design needs data or behavior that does not exist yet, route it explicitl
 - new or refreshed time-series/data pipeline:
   data publishing skill
 - operational/application records:
-  SimpleTable skill
+  MetaTable skill
 - widget-facing backend endpoint:
   API surfaces skill
 - custom form or interaction:

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/skills/dashboards/streamlit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mainsequence-dashboards-streamlit
-description: Use this skill when the task is about building a Streamlit dashboard in a Main Sequence project. This skill owns dashboard folder structure, app-owned page bootstrapping, sidebar and session patterns, optional instrument form usage, and dashboard-specific validation rules. It does not own FastAPI APIs, Command Center workspace documents, or release orchestration semantics.
+description: Use this skill when the task is about building a Streamlit dashboard in a Main Sequence project. This skill owns dashboard folder structure, app-owned page bootstrapping, sidebar and session patterns, and dashboard-specific validation rules. It does not own FastAPI APIs, Command Center workspace documents, or release orchestration semantics.
 ---
 
 # Main Sequence Streamlit Dashboards
@@ -14,7 +14,6 @@ This skill is for:
 - dashboard folder structure
 - app-owned Streamlit page bootstrapping
 - app-owned Streamlit helpers and components
-- optional instrument form rendering through `mainsequence.markets.instruments.streamlit`
 - dashboard-side reads from platform data products
 
 ## This Skill Can Do
@@ -24,8 +23,8 @@ This skill is for:
   - `app.py`
   - `README.md`
 - choose a plain Streamlit page bootstrap using `st.set_page_config(...)`
-- review dashboard-owned helpers for asset selection, valuation date settings, and user display
-- use the instrument form factory when the dashboard edits rich Pydantic models
+- review dashboard-owned helpers for entity selection, effective date settings, and user display
+- use model-driven form helpers when the dashboard edits rich Pydantic models
 - review dashboard reads from `APIDataNode` and other platform objects from the dashboard side
 - keep dashboard implementation aligned with Main Sequence packaging and release expectations
 
@@ -38,7 +37,7 @@ This skill must not claim ownership of:
 - AppComponent contracts
 - project-resource or release orchestration semantics
 - DataNode producer implementation
-- SimpleTable schema design
+- MetaTable schema design
 
 ## Route Adjacent Work
 
@@ -52,15 +51,14 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - DataNodes:
   `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
-- SimpleTables:
-  `.agents/skills/mainsequence/data_publishing/simple_tables/SKILL.md`
+- MetaTables:
+  `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 
 ## Read First
 
 1. `docs/tutorial/dashboards/streamlit/streamlit_integration_1.md`
 2. `docs/tutorial/dashboards/streamlit/streamlit_integration_2.md`
 3. `docs/knowledge/dashboards/streamlit/index.md`
-4. `docs/knowledge/dashboards/streamlit/instrument_forms.md`
 
 If the dashboard is being deployed or released, also read:
 
@@ -81,9 +79,9 @@ Before changing a Streamlit dashboard, collect or infer:
   - plain Streamlit only
   - app-owned helper components
 - whether the dashboard works with:
-  - assets
+  - data assets
   - valuation dates
-  - instrument configuration forms
+  - model configuration forms
 - which platform data products the dashboard reads
 
 If the dashboard root or entrypoint is unclear, stop before changing packaging-sensitive behavior.
@@ -96,7 +94,7 @@ For every non-trivial Streamlit dashboard task, decide:
 2. Does the root contain both `app.py` and `README.md`?
 3. What page setup and app-owned helper structure should the dashboard use?
 4. Which app-owned helper components should be reused instead of duplicating UI code?
-5. Does the dashboard need model-driven instrument forms?
+5. Does the dashboard need model-driven forms?
 6. Is the task really dashboard implementation, or is it actually an API, AppComponent, or release problem?
 
 ## Build Rules
@@ -146,8 +144,7 @@ Do not push producer semantics, release orchestration, or unrelated API logic in
 
 Examples:
 
-- keep asset selection and logged-user display as app-owned Streamlit helpers
-- use `mainsequence.markets.instruments.streamlit` for rich model-driven instrument forms when the optional extra is installed
+- keep logged-user display as app-owned Streamlit helpers
 - use `APIDataNode.build_from_identifier(...)` when a dashboard knows which published table it needs to read
 
 Do not push general-purpose dashboard UI helpers into the SDK.
@@ -169,7 +166,7 @@ When reviewing a Streamlit dashboard task, look for:
 - missing `README.md` next to `app.py`
 - stale imports from `mainsequence.dashboards.streamlit`
 - missing Streamlit dependencies in the dashboard project when the app imports Streamlit directly
-- hand-built model forms that should use the instrument form factory
+- hand-built model forms that should use model-driven helpers
 - dashboard code taking on API or release responsibilities
 - inconsistent page structure across a multipage app
 - dashboard logic that reads platform objects in an unclear or fragile way
@@ -182,7 +179,7 @@ Do not claim success until you have checked:
 - `README.md` exists next to `app.py`
 - pages use clear app-owned Streamlit setup
 - shared UI helper reuse is intentional and local to the dashboard project
-- instrument forms use the model-driven helpers when rich finance models are involved
+- model forms use the model-driven helpers when rich domain models are involved
 - the dashboard reads the intended published data products
 - the task did not confuse dashboard implementation with release orchestration or API design
 

{mainsequence-3.21.0 → mainsequence-4.0.3}/agent_scaffold/skills/data_access/exploration/SKILL.md

@@ -1,31 +1,31 @@
 ---
 name: mainsequence-data-exploration
-description: Use this skill when the task is to discover what `DataNode` or `SimpleTable` data already exists on the Main Sequence platform before implementation starts.
+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.
 ---
 
 # Main Sequence Data Exploration
 
 ## Overview
 
-Use this skill when the task is about discovering what `DataNode` or `SimpleTable` data is already available on the platform before implementation starts.
+Use this skill when the task is about discovering what `DataNode` 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 `SimpleTable`
-- which identifier, storage id, or object id should be used
+- whether the right surface is a `DataNode` 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
-- inspect published table identifiers, storage ids, and metadata
+- inspect published table identifiers, storage UIDs, and metadata
 - search for tables by keyword, description, or column name
 - inspect organization-visible table identifiers
-- inspect `SimpleTable` objects through the CLI
+- inspect registered `MetaTable` objects through the SDK client
 - summarize what data is available, what is missing, and what evidence supports that conclusion
 
 ## This Skill Must Not Claim
@@ -33,7 +33,7 @@ It helps answer questions such as:
 This skill must not claim ownership of:
 
 - producing or modifying `DataNode` pipelines
-- designing `SimpleTable` schemas or mutation behavior
+- designing `MetaTable` registration or operation behavior
 - deciding code-level read patterns for discovered datasets
 - building APIs or dashboards
 - scheduling jobs, images, or releases
@@ -47,16 +47,14 @@ This skill discovers and identifies data. It does not publish, redesign, or defi
   `.agents/skills/mainsequence/project_builder/SKILL.md`
 - `DataNode` creation or modification:
   `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
-- `SimpleTable` schema or updater work:
-  `.agents/skills/mainsequence/data_publishing/simple_tables/SKILL.md`
+- `MetaTable` registration or operation work:
+  `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - FastAPI or application-facing implementation:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
 - Streamlit dashboards:
   `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
 - Command Center surfaces:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
-- market-specific object discovery:
-  `.agents/skills/mainsequence/markets_platform/assets_and_translation/SKILL.md`
 - project-state reconciliation after exploration:
   `.agents/skills/mainsequence/maintenance/local_journal/SKILL.md`
 - blocker and failure analysis:
@@ -67,7 +65,7 @@ This skill discovers and identifies data. It does not publish, redesign, or defi
 1. `AGENTS.md`
 2. `docs/cli/index.md`
 3. `docs/knowledge/data_nodes.md`
-4. `docs/knowledge/simple_tables/simple_table.md` when the exploration touches row-oriented storage
+4. `docs/knowledge/meta_tables/index.md` when the exploration touches row-oriented storage
 
 ## Inputs This Skill Needs
 
@@ -76,14 +74,14 @@ Before exploring, collect or infer:
 - the business question being asked
 - whether the user is exploring organization-wide data or project-scoped data
 - whether the target is a published table or a row-oriented table
-- whether the user already knows an identifier, keyword, or object id
+- whether the user already knows an identifier, keyword, or object UID
 - whether metadata discovery alone answers the question
 
 ## Required Decisions
 
 For every non-trivial exploration task, decide:
 
-1. Is the data surface a `DataNode` or `SimpleTable`?
+1. Is the data surface a `DataNode` 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?
@@ -110,13 +108,11 @@ Typical commands include:
 - `mainsequence data-node list`
 - `mainsequence data-node list --show-filters`
 - `mainsequence data-node list --filter KEY=VALUE`
-- `mainsequence data-node detail <DATA_NODE_STORAGE_ID>`
-- `mainsequence simple_table list`
-- `mainsequence simple_table detail <SIMPLE_TABLE_ID>`
+- `mainsequence data-node detail <DATA_NODE_STORAGE_UID>`
 
 ### 2. Stop at discovery boundaries
 
-Use the CLI to identify what exists and collect the relevant identifiers, object ids, and metadata.
+Use the CLI or SDK client to identify what exists and collect the relevant identifiers, object UIDs, and metadata.
 
 Do not define code-level read patterns here.
 
@@ -131,7 +127,7 @@ For `DataNode` discovery specifically:
 When you say data exists, include the evidence you used:
 
 - identifier
-- storage id or object id
+- storage UID or object UID
 - object type
 - command used to discover it
 - metadata or filter evidence when available
@@ -143,7 +139,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 row-oriented operational data, hand off to `.agents/skills/mainsequence/data_publishing/simple_tables/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
 
 ## Review Rules
@@ -151,7 +147,7 @@ Examples:
 When reviewing an exploration result, look for:
 
 - a discovery claim without CLI evidence
-- confusion between `DataNode` and `SimpleTable`
+- confusion between `DataNode` and `MetaTable`
 - jumping into implementation work before discovery is complete
 - claiming implementation conclusions from a discovery-only pass
 
@@ -161,7 +157,7 @@ Do not claim exploration success until you have checked:
 
 - the correct platform surface was identified
 - CLI discovery was used first
-- existing identifiers or object ids were captured
+- existing identifiers or object UIDs were captured
 - the result clearly distinguishes:
   - what exists
   - what is missing