mainsequence-metatable 0.1.58.dev89__tar.gz → 0.1.59.dev90__tar.gz

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/.agents/skills/client/metatables-meta-tables/SKILL.md

@@ -108,8 +108,8 @@ revisions; do not recompute identity from columns or rewrite applied history.
 
 A password, API key, token or similar value that an application stores in a table
 is declared with `EncryptedString`, never with `String`
-([ADR 0025](../../../../docs/adr/client/0025-application-encrypted-columns.md),
-[guide](../../../../docs/client/define-and-migrate-tables.md#protect-a-column-with-application-encryption)).
+(ADR 0025, `docs/adr/client/0025-application-encrypted-columns.md`; guide section
+"Protect a column with application encryption" in `docs/client/define-and-migrate-tables.md`).
 Table grants decide who reads the row; the Secret decides who reads the value.
 
 ```python

mainsequence_metatable-0.1.59.dev90/.agents/skills/ms_tau_sdk/PINNED_FROM.txt

@@ -0,0 +1,7 @@
+schema=1
+library_name=ms-tau-sdk
+namespace=ms_tau_sdk
+pinned_version=2.0.26
+skills_path=src/ms_tau_sdk/agent_skills
+skills=design-agent-icons-and-motion,tau_a2a_runtime_adapter,tau_local_development,tau_project_customization,tau_repository_integration,tau_security_and_access
+command=ms-tau skills sync --path .

mainsequence_metatable-0.1.59.dev90/.agents/skills/ms_tau_sdk/design-agent-icons-and-motion/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: design-agent-icons-and-motion
+description: Offer general composition and motion guidance when designing or reviewing agent icons. Use for visual identity work, not conversation or session implementation.
+---
+
+# Agent Icon Composition and Motion
+
+These are suggestions. Adapt them to the user's direction, the project's identity and the host.
+
+Keep each agent's artwork, animations and build files in its owning project. `ms-tau-sdk`
+distributes general guidance and this worked example; it does not own project or provider assets.
+
+## Composition
+
+- Start with the project's or provider's actual logo and preserve its recognisable shape.
+- Keep one clear visual focus, balanced spacing and enough empty space for motion.
+- Use consistent proportions, stroke weight and restrained accents to relate a family without
+  making its members indistinguishable. Avoid adding detail that disappears at display size.
+- Fit the host's typography, colours and surfaces; check contrast in both themes.
+
+## Motion
+
+- Consider animation for every agent, with quiet idle motion and distinct activity motion.
+- Keep the identity readable while a supporting element communicates activity.
+- Let motion reflect the agent's purpose and reported state; never imply unreported progress
+  or success. Prefer restrained movement and smooth loop seams.
+- Provide a useful still and respect reduced motion.
+
+## Worked Example: MetaTables
+
+Read or open [the visual walkthrough and editable source](references/metatables-example.html).
+It builds the real logo into three layers, shows four animated states and actual display sizes,
+and includes light/dark and reduced-motion checks. Expand its source section to see the SVG
+composition and CSS that draw those same previews.
+
+Follow the walkthrough's adaptation steps: preserve the next project's identity, reserve space
+for activity, and design an accent that reflects its purpose. The example's coordinates and
+row-scanning motif explain one solution; they are not a template every agent must copy.
+
+Review at the actual display size, checking recognition, spacing, clipping and both themes.
+Check the target renderer's supported formats, size limits and states before integration. Keep
+this design work within the requested scope; it does not itself publish or replace live icons.

mainsequence_metatable-0.1.59.dev90/.agents/skills/ms_tau_sdk/design-agent-icons-and-motion/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Agent Icons and Motion"
+  short_description: "Optional guidance for agent logos and action motion"
+  default_prompt: "Use $design-agent-icons-and-motion to suggest an agent icon family using existing logos and action-specific motion, adapted to the host and the user's preferences."

mainsequence_metatable-0.1.59.dev90/.agents/skills/ms_tau_sdk/design-agent-icons-and-motion/references/metatables-example.html

@@ -0,0 +1,146 @@
+<!doctype html>
+<html lang="en" data-theme="dark">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>MetaTables — a worked icon composition</title>
+<style id="example-styles">
+:root { color-scheme: dark; --bg:#191919; --surface:#222222; --ink:#eeeae4; --muted:#aaa7a2; --line:#383838; }
+:root[data-theme="light"] { color-scheme:light; --bg:#f7f6f3; --surface:#fff; --ink:#292928; --muted:#65635f; --line:#dedcd7; }
+* { box-sizing:border-box; }
+body { margin:0; background:var(--bg); color:var(--ink); font:15px/1.55 -apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif; }
+main { max-width:1080px; margin:auto; padding:36px 28px 48px; }
+header { display:flex; justify-content:space-between; align-items:center; gap:16px; }
+.eyebrow { color:var(--muted); font-size:11px; letter-spacing:.12em; text-transform:uppercase; }
+.controls { display:flex; gap:8px; }
+button, summary { font:inherit; cursor:pointer; }
+button { color:var(--ink); background:var(--surface); border:1px solid var(--line); border-radius:20px; padding:7px 14px; }
+button:hover { border-color:var(--muted); }
+button:focus-visible, summary:focus-visible { outline:2px solid var(--ink); outline-offset:4px; }
+button:disabled { cursor:default; opacity:.65; }
+h1 { font-size:36px; font-weight:550; line-height:1.2; letter-spacing:-.035em; margin:32px 0 10px; }
+h2 { font-size:20px; font-weight:550; margin:30px 0 14px; letter-spacing:-.02em; }
+h3 { font-size:15px; font-weight:550; margin:10px 0 4px; }
+p { margin:0 0 12px; }
+.intro { color:var(--muted); max-width:780px; }
+.build { display:grid; grid-template-columns:repeat(3,1fr); gap:12px; }
+.card { border:1px solid var(--line); background:var(--surface); border-radius:16px; padding:18px 20px; }
+.step { font:11px ui-monospace,SFMono-Regular,monospace; color:var(--muted); }
+.diagram { display:flex; justify-content:center; align-items:center; height:145px; }
+.diagram svg { width:128px; height:128px; overflow:visible; }
+.caption { color:var(--muted); font-size:13px; }
+code { font-family:ui-monospace,SFMono-Regular,monospace; font-size:.86em; }
+.measure { stroke:currentColor; opacity:.16; fill:none; stroke-width:.35; stroke-dasharray:1 1; }
+.states { display:grid; grid-template-columns:repeat(4,1fr); gap:12px; }
+.state { padding:16px 18px; }
+.state svg { display:block; width:72px; height:72px; margin:6px 0 12px; }
+.state p { color:var(--muted); font-size:12px; margin:0; }
+.samples { display:flex; align-items:center; gap:26px; padding:18px 0; flex-wrap:wrap; }
+.sample { display:flex; align-items:center; gap:10px; }
+.sample span { font-size:12px; color:var(--muted); }
+.sample svg { display:block; }
+.note { color:var(--muted); font-size:12px; border-top:1px solid var(--line); padding-top:14px; }
+details { border:1px solid var(--line); border-radius:12px; padding:14px 18px; margin-top:18px; }
+summary { font-size:14px; }
+pre { background:var(--surface); border-radius:8px; padding:16px; font-size:11px; line-height:1.65; overflow:auto; max-height:400px; }
+.recipe { padding-left:20px; font-size:13px; }
+.recipe li { padding-left:4px; margin:10px 0; }
+/* Only supporting marks animate. The logo and lower-left signature stay fixed. */
+.icon { color:var(--ink); }
+.signature { fill:none; stroke:currentColor; stroke-width:2.5; stroke-linecap:round; }
+.node { fill:currentColor; }
+.pulse { animation:breathe 4.8s ease-in-out infinite; }
+.orbit { transform-origin:35.5px 4.5px; animation:gather 2.4s linear infinite; }
+.rows { fill:none; stroke:currentColor; stroke-width:1.3; stroke-linecap:round; opacity:.2; }
+.scan { fill:none; stroke:currentColor; stroke-width:1.6; stroke-linecap:round; animation:scan-rows 2.4s steps(1,end) infinite; }
+.attention { fill:none; stroke:currentColor; stroke-width:1.4; animation:breathe 2.4s ease-in-out infinite; }
+@keyframes breathe { 0%,100% { opacity:.5; } 50% { opacity:1; } }
+@keyframes gather { to { transform:rotate(360deg); } }
+@keyframes scan-rows { 0% { transform:translateY(0); } 33.333% { transform:translateY(2.2px); } 66.667% { transform:translateY(4.4px); } }
+[data-paused="true"] .pulse, [data-paused="true"] .orbit, [data-paused="true"] .scan, [data-paused="true"] .attention { animation-play-state:paused; }
+@media (prefers-reduced-motion:reduce) { .pulse,.orbit,.scan,.attention { animation:none; } }
+@media(max-width:700px) { main { padding:24px 16px; } header { align-items:flex-start; flex-direction:column; } h1 { font-size:30px; } .build { grid-template-columns:1fr; } .diagram { height:130px; } .states { grid-template-columns:repeat(2,1fr); } }
+</style>
+</head>
+<body>
+<!-- Original project geometry; fill uses the surrounding host ink. Teaching reference only. -->
+<svg width="0" height="0" style="position:absolute" aria-hidden="true"><defs>
+<symbol id="metatables-mark" viewBox="0 0 64 64">
+  <circle cx="11" cy="13" r="5" fill="currentColor"/>
+  <circle cx="11" cy="51" r="5" fill="currentColor"/>
+  <circle cx="26" cy="32" r="4.5" fill="currentColor"/>
+  <path fill="currentColor" d="M10.86 16.97 13.15 15.03 24.15 28.03 21.86 29.97Z"/>
+  <path fill="currentColor" d="M10.86 47.03 13.15 48.97 24.15 35.97 21.86 34.03Z"/>
+  <path fill="currentColor" fill-rule="evenodd" d="M32 20h25v24H32Z M35 23h5v4h-5Z M42 23h5v4h-5Z M49 23h5v4h-5Z M35 29h5v5h-5Z M42 29h5v5h-5Z M49 29h5v5h-5Z M35 36h5v5h-5Z M42 36h5v5h-5Z M49 36h5v5h-5Z"/>
+</symbol>
+</defs></svg>
+<main>
+<header><span class="eyebrow">MainSequence / Composition reference</span><div class="controls"><button id="theme" type="button">Use light theme</button><button id="motion" type="button" aria-pressed="false">Pause motion</button></div></header>
+<h1>Build the MetaTables icon.</h1>
+<p class="intro">One worked example: preserve the project mark, compose a quiet family signature, then add a separate activity layer. The dimensions below explain this composition; adapt them to the next logo.</p>
+<h2>1. Build three layers</h2>
+<section class="build" aria-label="Composition walkthrough">
+<article class="card"><span class="step">01 / IDENTITY</span><div class="diagram" id="identity"></div><h3>Keep the real mark</h3><p class="caption">Place the unchanged logo in a <code>26 × 26</code> box at <code>(7, 7)</code> on a <code>40 × 40</code> canvas. The table cells and relationship nodes stay legible.</p></article>
+<article class="card"><span class="step">02 / FAMILY SIGNATURE</span><div class="diagram" id="composition"></div><h3>Balance the corners</h3><p class="caption">Add a detached node at <code>(35.5, 4.5)</code> and a short lower-left diagonal. Keep both outside the logo. Dashed boxes show the reserved space.</p></article>
+<article class="card"><span class="step">03 / ACTIVITY</span><div class="diagram" id="activity"></div><h3>Scan below the identity</h3><p class="caption">Reserve <code>y = 34.2…38.6</code> for three short rows. Highlight one row at a time while working. The logo stays fixed; the accent carries the motion.</p></article>
+</section>
+<h2>2. Change the accent with the state</h2>
+<section class="states" aria-label="Animated states">
+<article class="card state"><div data-state="idle"></div><h3>Idle</h3><p>Node opacity breathes over 4.8 s. Identity stays still.</p></article>
+<article class="card state"><div data-state="thinking"></div><h3>Thinking</h3><p>Three small signals orbit the node. No table scan yet.</p></article>
+<article class="card state"><div data-state="working"></div><h3>Working</h3><p>A highlight scans three rows over 2.4 s. Activity, not progress.</p></article>
+<article class="card state"><div data-state="error"></div><h3>Needs attention</h3><p>The node becomes a gently pulsing diamond. No flashing.</p></article>
+</section>
+<div class="samples" aria-label="Working icon at actual display sizes"><span class="eyebrow">Check at display size</span><div class="sample" data-size="24"></div><div class="sample" data-size="32"></div><div class="sample" data-size="48"></div></div>
+<p class="note" id="motion-note">Motion here demonstrates design states. In the host, use reported agent activity. Pause and reduced motion preserve a readable frame.</p>
+<details open><summary>3. Adapt this composition to another project</summary><ol class="recipe"><li><strong>Replace the identity layer.</strong> Keep that project's real mark and adjust its optical size. Do not copy MetaTables' table imagery to an unrelated agent.</li><li><strong>Keep a clear activity area.</strong> This example uses the lower band. A wider or taller logo may need another placement or less detail.</li><li><strong>Choose one relevant action.</strong> The moving row communicates the work of this agent. Design the next project's accent around its own purpose.</li><li><strong>Verify the result.</strong> Inspect both themes, small sizes, stills and the loop. This HTML uses SVG/CSS for explanation; export the owning project's assets in the target host's supported format.</li></ol></details>
+<details><summary>Editable source: logo, composition and animation</summary><p class="caption" style="margin-top:14px">This file is the complete runnable example. The excerpts below are read from the same source that draws the previews.</p><h3>Original logo geometry</h3><pre><code id="source-logo"></code></pre><h3>Composition and state selection</h3><pre><code id="source-composition"></code></pre><h3>Motion rules</h3><pre><code id="source-motion"></code></pre></details>
+<p class="note" style="margin-top:20px">Source mark: MetaTables project's <code>public/navigation-icon.svg</code>, reproduced here as a teaching reference with its geometry preserved and fill set to <code>currentColor</code>. Production artwork and build tooling belong to the owning project. This example makes no backend requests and changes no installed icons.</p>
+</main>
+<script>
+function drawIcon(state, {guides=false, layer='activity', size=128}={}) {
+  const identity = '<use data-layer="identity" href="#metatables-mark" x="7" y="7" width="26" height="26"/>';
+  const signature = '<path class="signature" d="M4.5 35.5l3-3"/>';
+  const node = '<circle class="node" cx="35.5" cy="4.5" r="2"/>';
+  const accent = {
+    idle:'<circle class="node pulse" cx="35.5" cy="4.5" r="2"/>',
+    thinking:'<g class="orbit"><circle class="node" cx="37.6" cy="4.5" r="1.2"/><circle class="node" cx="34.45" cy="6.32" r=".8" opacity=".65"/><circle class="node" cx="34.45" cy="2.68" r=".8" opacity=".4"/></g>',
+    working:node+'<path class="rows" d="M14 34.2h14m-14 2.2h14m-14 2.2h14"/><path class="scan" d="M14 34.2h14"/>',
+    error:'<path class="attention" d="m35.5 1.2 3.3 3.3-3.3 3.3-3.3-3.3Z"/>'
+  }[state];
+  const grid = guides ? '<rect class="measure" x=".5" y=".5" width="39" height="39"/><rect class="measure" x="7" y="7" width="26" height="26"/>' : '';
+  const accents = layer === 'identity' ? '' : signature + (layer === 'signature' ? node : accent);
+  return `<svg class="icon" viewBox="0 0 40 40" width="${size}" height="${size}" role="img" aria-label="MetaTables ${state}">${grid}${identity}<g data-layer="activity">${accents}</g></svg>`;
+}
+document.querySelector('#identity').innerHTML=drawIcon('idle',{guides:true,layer:'identity'});
+document.querySelector('#composition').innerHTML=drawIcon('idle',{guides:true,layer:'signature'});
+document.querySelector('#activity').innerHTML=drawIcon('working',{guides:true});
+document.querySelectorAll('[data-state]').forEach(el=>el.innerHTML=drawIcon(el.dataset.state));
+document.querySelectorAll('[data-size]').forEach(el=>el.innerHTML=drawIcon('working',{size:Number(el.dataset.size)})+`<span>${el.dataset.size} px</span>`);
+document.querySelector('#source-logo').textContent=document.querySelector('#metatables-mark').outerHTML;
+document.querySelector('#source-composition').textContent=drawIcon.toString();
+document.querySelector('#source-motion').textContent=document.querySelector('#example-styles').textContent.split('/* Only supporting marks animate. The logo and lower-left signature stay fixed. */')[1].split('@media(max-width:700px)')[0];
+const root=document.documentElement;
+document.querySelector('#theme').onclick=()=>{
+  root.dataset.theme=root.dataset.theme==='dark'?'light':'dark';
+  document.querySelector('#theme').textContent=`Use ${root.dataset.theme==='dark'?'light':'dark'} theme`;
+};
+const motion=document.querySelector('#motion');
+const reduced=matchMedia('(prefers-reduced-motion: reduce)');
+function applyPreference(){
+  motion.disabled=reduced.matches;
+  root.dataset.paused=String(reduced.matches);
+  motion.setAttribute('aria-pressed',String(reduced.matches));
+  motion.textContent=reduced.matches?'Reduced motion':'Pause motion';
+}
+motion.onclick=()=>{
+  const paused=root.dataset.paused!=='true';
+  root.dataset.paused=String(paused);
+  motion.setAttribute('aria-pressed',String(paused));
+  motion.textContent=paused?'Play motion':'Pause motion';
+};
+reduced.addEventListener('change',applyPreference);
+applyPreference();
+</script>
+</body>
+</html>

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/.agents/skills/ms_tau_sdk/tau_a2a_runtime_adapter/SKILL.md

@@ -32,7 +32,9 @@ The SDK owns:
   which the platform's own records establish, never the `X-Caller-*` headers;
 - presenting the verified caller assertion of the request that starts a chat or A2A Message turn
   only when it marks that turn active, so that the platform can record the turn's requester;
-  taking the person the turn serves only from the platform's answer to the turn start; and giving
+  taking the person a chat, A2A Message or caller-delivery turn serves from the platform's answer
+  to the turn start, and the person a Task attempt serves from the platform's answer to the Task's
+  creation or continuation or from its dispatch; and giving
   extension tools that person and calls for the work through `current_requester()` and
   `platform_client()` without exposing the assertion, the lease proof, or any token;
 - translating inbound A2A requests into the shared TAU runtime; and

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/.agents/skills/ms_tau_sdk/tau_project_customization/SKILL.md

@@ -15,30 +15,54 @@ The workspace `.tau/` directory is the project behavior boundary:
 
 ```text
 .tau/
-├── SYSTEM.md
+├── SYSTEM.md            replaces the packaged system prompt
+├── APPEND_SYSTEM.md     appended to the system prompt
+├── AGENTS.md            project instructions for the deployed Agent
 ├── prompts/
 ├── skills/
 └── extensions/
 ```
 
 Creating `.tau/SYSTEM.md` replaces the packaged default general system instructions. There is no
-second SDK-specific prompt override or companion append file. Other resources follow the TAU
-version pinned by the installed SDK.
-
-`.agents/skills/ms_tau_sdk/` is different: it contains managed development instructions for coding
-agents working on the repository. It is not the runtime's `.tau` behavior and must not be used as
-application configuration.
-
-Tau reads skills in `.tau/skills/` and `.agents/skills/` at any depth: a folder without a
-`SKILL.md` groups skills, such as `.agents/skills/mcp_tools/<skill>/SKILL.md`, the folder an
-application can publish with the mainsequence SDK's skills publisher. The managed skills in
-`.agents/skills/ms_tau_sdk/` are read too.
+SDK-specific prompt setting; Tau's own `APPEND_SYSTEM.md` and `AGENTS.md` under `.tau/` are the
+other prompt resources. Other resources follow the TAU version pinned by the installed SDK.
+
+By default the deployed Agent reads `.tau/` and nothing else in the repository. The root
+`AGENTS.md` and `.agents/` hold instructions for coding agents working on the repository, you
+among them: `.agents/skills/ms_tau_sdk/` is this SDK's managed development bundle,
+`.agents/skills/mainsequence/` the platform SDK's, and the repository adds its own. None of it is
+runtime behavior, none of it reaches the Agent, and none of it may be used as application
+configuration. Put instructions meant for the Agent in `.tau/AGENTS.md`, `.tau/APPEND_SYSTEM.md`
+or `.tau/SYSTEM.md`. Only an Agent that is itself a coding agent over its repository sets
+`TAU_INCLUDE_DEVELOPMENT_RESOURCES=true`, which reads the root `AGENTS.md` and `.agents/` as well.
+
+Tau reads the Agent's skills in `.tau/skills/` at any depth: a folder with a `SKILL.md` is a skill,
+named after its folder; a folder without one groups skills, such as
+`.tau/skills/<group>/<skill>/SKILL.md`. When the application also publishes the Agent's usage skills
+to other agents with the mainsequence SDK's `skills_extension`, point the publisher at `.tau/skills`
+itself: the Agent's skills and the published skills are one set. Do not publish a group folder
+inside it to keep some skills private; instructions other agents may not see belong in
+`.tau/SYSTEM.md` or `.tau/AGENTS.md`. The publisher's rules then hold for the whole folder:
+lowercase letters, digits and single hyphens in every skill and group folder name; every folder a
+skill or a non-empty group; frontmatter `name` equal to the folder name; leaf folder names unique,
+because Tau names a skill by its folder. A group folder prefixes the published `skill://` URIs, so
+a pack that was published from its own folder moves its skills directly into `.tau/skills` to keep
+its URIs. Development skills stay in `.agents/skills` and are never published.
+
+## Agent artwork
+
+For optional icon composition and motion guidance, use `design-agent-icons-and-motion` from
+this SDK's skill bundle. It includes a worked visual example; project artwork and animations
+remain owned by the project.
 
 ## Extension ownership
 
 Project extensions belong under `.tau/extensions/` and may add tools, hooks, and lifecycle
 behavior. Keep reusable business logic in the normal application package and make extension
-adapters thin and structured.
+adapters thin and structured. When Main Sequence hosts the runtime, list every package an
+extension imports in the repository's committed `requirements.txt`, and import the project's own
+packages from `src/` or the repository root, because the project itself is not installed;
+`tau-repository-integration` says how to keep that file current.
 
 The project author owns:
 
@@ -53,12 +77,14 @@ tools are project choices and are not part of the base SDK.
 
 ## Runtime tool composition
 
-Two independent process settings select the host-provided tools. Both default to `false`:
+Three independent process settings select the host-provided tools and the reading scope. All
+default to `false`:
 
 | Setting | Effect when `true` |
 | --- | --- |
 | `TAU_EXCLUDE_BASE_TOOLS` | Replace Tau's `read`, `write`, `edit`, and `bash` with a skill-scoped `read`. |
 | `TAU_EXCLUDE_MAINSEQUENCE_MCP` | Skip Main Sequence MCP connection, tools, resources, and resource prompt. |
+| `TAU_INCLUDE_DEVELOPMENT_RESOURCES` | Read the repository as a coding harness: the root `AGENTS.md`, every `AGENTS.md` above the workspace, `.agents/AGENTS.md`, `.agents/skills` and `.agents/prompts`, beside `.tau`. |
 
 Set them in `harness_agent.spec.env_vars` in a managed repository workflow, in the process
 environment for local `ms-tau`, or through explicit `TauSDKSettings` fields in a Python host. They
@@ -107,7 +133,7 @@ A declared application can publish Agent Skills through the MCP Skills extension
 mainsequence SDK's skills publisher does. The Agent lists them with `<name>__list_resources` and
 reads one file with `<name>__read_resource`; a skill file is returned only when its bytes match the
 size and SHA-256 digest the skill lists. Published skills stay the application's: they are not
-project skills under `.tau/skills/`, and fields such as `allowed-tools` grant nothing. With the
+added to this Agent's skills under `.tau/skills/`, and fields such as `allowed-tools` grant nothing. With the
 coding tools, a model that follows a published skill can run commands; set
 `TAU_EXCLUDE_BASE_TOOLS=true` when that must not happen.
 
@@ -183,8 +209,8 @@ Rules for tools that act for the requester:
   credentials itself. A tool never reads, logs, stores, or forwards them, passes a path rather than
   a URL, and never sets `Authorization` or an `X-MainSequence-*` header.
 - A delegated call uses the person's ordinary permissions, including administrative ones; any other
-  call uses the Agent's own. Each operation decides what it needs. Never infer write permission
-  from read access.
+  call uses the Agent's own. Each operation decides what it needs: never infer that a call may
+  change an object because it may read it.
 - Return to the model only business results, such as rows, numbers, and names. Never return the
   response object, its headers, a token, a proof, or a raw error body.
 - Keep nothing for another turn or another person. The delegation ends with the turn, and a task
@@ -206,8 +232,8 @@ separate authority. Prompt injection can cause unintended changes, sharing, or d
 person's permissions, and completed writes can outlast the delegation. Only Organization admins
 enable this authority.
 
-For a complete example, a tool that uses a person's Secret without exposing it, and how sharing
-decides what a delegated call can reach, use `tau_security_and_access`.
+For a complete example, a tool that uses a person's Secret without exposing it, and how policies
+decide what a delegated call can reach, use `tau_security_and_access`.
 
 ## Validation
 

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/.agents/skills/ms_tau_sdk/tau_repository_integration/SKILL.md

@@ -22,6 +22,8 @@ uv run ms-tau skills sync --path .
 
 This command atomically owns only `.agents/skills/ms_tau_sdk/`. Do not copy these files manually,
 edit the managed copies, or make installation and runtime startup synchronize them implicitly.
+These are development instructions for coding agents; the Agent the repository deploys reads its
+resources from `.tau/` only and never sees `.agents/` or the root `AGENTS.md`.
 
 ## Service entry points
 
@@ -58,6 +60,25 @@ only with that declaration, read from the object it serves. Therefore:
   repository. The platform sets them when it hosts the runtime, and local mode refuses to start
   with them.
 
+## Hosted dependencies and code
+
+When Main Sequence hosts the runtime, it installs the packages that the committed
+`requirements.txt` at the repository root lists, or, without that file, the dependencies that the
+root `pyproject.toml` declares, and reuses them for every later commit until the file or the base
+image changes. A package that `pyproject.toml` declares but `requirements.txt` does not list,
+`ms-tau-sdk` included, is not installed, and its import fails in the hosted runtime. After adding
+or upgrading the SDK, or a package that project code or an extension imports, run
+`mainsequence code-repository sync` and commit `requirements.txt` with `uv.lock`. Pin the SDK from
+the package index or a Git commit, never from a local path: the hosted build refuses local paths
+other than the repository itself, and `-r` or `-c` references.
+
+The hosted runtime runs the repository's files from `/workspace`, its working directory and
+therefore the SDK workspace, with `/workspace/src` and `/workspace` on `PYTHONPATH`. The project
+itself is not installed. Keep its top-level packages directly under `src/` or the repository root,
+and do not make project code or extensions depend on `importlib.metadata` for the project's own
+version or entry points, on the project's own console scripts, or on extensions compiled from its
+sources.
+
 ## Job-hosted batch execution
 
 ADR 0015 accepts a Python batch entry point, but it is **not implemented in this SDK version**.
@@ -96,7 +117,8 @@ JobRun UID in the SDK.
 ## Repository integration procedure
 
 1. Inspect the project's Python constraint, dependency manager, lockfile, and application layout.
-2. Add and pin `ms-tau-sdk` through that existing dependency workflow.
+2. Add and pin `ms-tau-sdk` through that existing dependency workflow. For a runtime that Main
+   Sequence hosts, refresh and commit `requirements.txt` as "Hosted dependencies and code" says.
 3. Synchronize these skills explicitly with `uv run ms-tau skills sync --path .`.
 4. For a service, use `uv run ms-tau` unless the repository needs an importable ASGI module.
    For a finite Job, follow the batch design only after the installed SDK supports it.
@@ -126,5 +148,12 @@ uv run python -c "from api.tau.main import app; print(app.state.mainsequence_req
 The second command prints `{'installed': True, 'mode': 'local', 'public_ingress': ()}` outside
 hosting.
 
+For a runtime that Main Sequence hosts, also check that the committed `requirements.txt` pins the
+SDK; the command prints its line:
+
+```bash
+grep -i '^ms-tau-sdk' requirements.txt
+```
+
 Do not require the `mainsequence` Python distribution in the TAU dependency graph. Authentication
 and Main Sequence transport are implemented directly by `ms-tau-sdk`.

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/.agents/skills/ms_tau_sdk/tau_security_and_access/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tau-security-and-access
-description: Build and review project tools that call the platform or other applications for the person a turn serves, including tools that use a person's Secret without exposing it, and explain how delegation and sharing decide what those tools can reach.
+description: Build and review project tools that call the platform or other applications for the person a turn serves, including tools that use a person's Secret without exposing it, and explain how delegation and policies decide what those tools can reach.
 ---
 
 # TAU Security and Access
@@ -8,7 +8,7 @@ description: Build and review project tools that call the platform or other appl
 Use this skill when a project tool under `.tau/extensions/` calls the platform or another
 platform application, uses a Secret, or must answer each person with their own data. Extension
 mechanics are in `tau_project_customization`. The full model, with the administrator setup, is in
-the SDK's Security and access guide (`docs/reference/security-model.md`). Sharing itself is in
+the SDK's Security and access guide (`docs/reference/security-model.md`). Managing policies is in
 `.agents/skills/mainsequence/platform_operations/access_control_and_sharing/SKILL.md`.
 
 ## Who a call acts as
@@ -21,12 +21,14 @@ Every call a tool makes through `platform_client()` follows one rule:
 | A valid delegation | The person the turn serves, with their ordinary permissions, including administrative ones. |
 | A delegation that ended or is invalid | None. The call is refused with a `PermissionError` and is never retried as the Agent. |
 
-- The platform names the person when the turn starts, and `current_requester()` returns them. It
+- The platform names the person when a chat or Message turn starts, and for a Task when it is
+  created, continued or dispatched; `current_requester()` returns them. It
   returns `None` when the Agent is not enabled to act for people (only an Organization admin can
   enable it, with `acts_for_requester`), for work no person asked for, in local mode and outside a
   turn.
 - The operation or application that receives the call decides what it may do. No list says which
-  operations accept a delegation. Read access never implies edit, run, share or delete.
+  operations accept a delegation. On the platform, each operation needs its own action: reading an
+  object never lets the call change, run or delete it, or decide who has access.
 - The call stays the Agent's call, made for the person. It is not impersonation: the platform
   checks it on every call, only while the turn or Task serving the person runs, for at most 24
   hours after their request, and only in the Agent's Environment.
@@ -175,40 +177,42 @@ What makes it safe:
 - The Agent's own workload holds no grant on these Secrets, so a call without the person reaches
   none of them.
 
-## Sharing decides what a delegated call can reach
+## Policies decide what a delegated call can reach
 
-A delegated read returns anything the person can view in the Agent's Environment: what they
-created and what others shared with them, directly or through a team. This holds for Secrets and
-other shared resources. A team's members receive what is shared with it, and `in_teams()` answers
-membership. Who can see and manage a team is decided separately, by the `viewer`,
-`membership_manager`, `editor` and `owner` policies on it: any person can create a team and
-becomes its owner and first member, members can see the team and leave it, and Organization admins
-manage every team from their role, without being members. No membership is protected. See the SDK
-Security and access guide's **Teams and membership** section. The platform enforces sharing;
-which of those objects a tool uses is part of the tool's design. For Secrets, the naming
-convention states that design:
+A delegated call reaches what the person's policies allow in the Agent's Environment: the policies
+they hold directly, such as `owner` on what they created, and those given to a team they belong to.
+This holds for Secrets and every other object the platform decides by policies. A team's members
+receive the policies given to it, and `in_teams()` answers membership. Who can see and manage a
+team is decided separately, by the `viewer`, `membership_manager`, `editor` and `owner` policies on
+it: any person can create a team and becomes its owner and first member, members can see the team
+and leave it, and Organization admins manage every team from their role, without being members.
+See the SDK Security and access guide's **Teams and membership** section. The platform enforces
+the policies; which of those objects a tool uses is part of the tool's design. For Secrets, the
+naming convention states that design:
 
 - **A personal credential:** a name tied to the person, such as `QUOTES_API_KEY__<person uid>`.
-  The person decides whether to share it.
+  The person owns it and decides whether anyone else gets a policy on it.
 - **A team credential:** a name the team agrees on, with `value_reader` attached to the team. The
   tool reads it for any member.
-- **Someone else's Secret shared with the person:** valid whenever the tool is meant to use it.
+- **Someone else's Secret whose value the person may read:** valid whenever the tool is meant to
+  use it.
 
-Whoever can edit a Secret decides its value, so the tool uses whatever value they set. Granting or
-accepting edit on a Secret means trusting that person with what the tool does with it. That is a
-decision people make through sharing, not one the platform makes for them.
+Whoever holds `editor` or `owner` on a Secret sets its value, so the tool uses whatever value they
+set. Giving someone either policy on a Secret, or using a Secret whose editors or owners are other
+people, means trusting them with what the tool does with it. That is a decision people make when
+they give policies, not one the platform makes for them.
 
-How sharing works:
+How Secret policies work:
 
 - Policies on a Secret decide access: `reader` sees that it exists and its name, never its value;
   `value_reader` also reads the current value; `editor` also reads earlier values, sets a new value,
   deletes it and sees who has access; `owner` also decides who has access. The creator becomes its
   owner, and Organization admins hold every policy on their Organization's Secrets from their role.
 - Owners attach and detach these policies for people, teams and workloads; whoever manages a
-  workload can also give it a policy they hold, and anyone can remove their own. No policy is
-  protected: an owner can remove the creator's. Nobody gives a policy with more than they hold, and
-  people other than Organization admins give access only to people who share an active team with
-  them, to teams they belong to and to workloads they can view.
+  workload can also give it a policy they hold, and anyone can remove their own. Nobody gives a
+  policy with more than they hold, and people other than Organization admins give access only to
+  people who share an active team with them, to teams they belong to, and to workloads they manage
+  or whose Job or release they can see (`jobs.read` or `resource-releases.read`).
 - `GET /api/v1/secrets/<uid>/access/` lists who holds which policy, for editors and owners, and
   `GET /api/v1/secrets/<uid>/access/me/` answers what the caller may do with it. A tool can use
   them when its design needs to, for example to refuse a team key where it expects a personal one.
@@ -265,9 +269,9 @@ platform checks it again on every call.
 
 ## Checking the person's teams
 
-A delegated call already reaches exactly what the person can, including what is shared with their
-teams, so a tool rarely checks teams itself. When the tool's own policy names teams, ask the
-platform with `in_teams()`:
+A delegated call already reaches exactly what the person can, including what the policies given to
+their teams allow, so a tool rarely checks teams itself. When the tool's own policy names teams,
+ask the platform with `in_teams()`:
 
 ```python
 person = current_requester()
@@ -328,7 +332,7 @@ Patch the extension module's `current_requester` and `platform_client` with fake
 - No person's UID, Secret name or Secret value comes from tool arguments, the prompt or history.
 - No tool returns a credential or calls a platform path the model chooses.
 - Secret values stay inside one call, in headers, never in results, logs, errors, URLs or caches.
-- The naming convention says whose Secrets the tool uses, and the people sharing them know it.
+- The naming convention says whose Secrets the tool uses, and the owners of those Secrets know it.
 - A refused delegated call is reported, never retried as the Agent.
 - The Agent's workload holds no grants it does not need, and none on people's Secrets; `user` is
   enough on an Agent it only sends work to.

{mainsequence_metatable-0.1.58.dev89/src/mainsequence_metatable.egg-info → mainsequence_metatable-0.1.59.dev90}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.58.dev89
+Version: 0.1.59.dev90
 Summary: Main Sequence MetaTables Python client and standalone API
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT
@@ -52,7 +52,7 @@ Requires-Dist: twine<7,>=6; extra == "dev"
 Provides-Extra: docs
 Requires-Dist: mkdocs<2,>=1.6; extra == "docs"
 Provides-Extra: agent
-Requires-Dist: ms-tau-sdk==2.0.18; extra == "agent"
+Requires-Dist: ms-tau-sdk==2.0.26; extra == "agent"
 Provides-Extra: mysql
 Requires-Dist: PyMySQL[rsa]<1.2,>=1.1.1; extra == "mysql"
 Provides-Extra: mssql

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/docs/adr/agent/0019-metatables-analyst-agent.md

@@ -1,5 +1,13 @@
 # ADR 0019: MetaTables Analyst agent
 
+> Amendment (2026-10-27): ms-tau-sdk 2.0.26 (its ADR 0025) gives a deployed Agent only
+> `.tau/`: skills from `.tau/skills/`, no `AGENTS.md` and nothing under `.agents/`.
+> `discover-tables` and `analyze-with-sql` move to `.tau/skills/`, beside the vendored
+> pg-aiguide skills, and the agent card points there. The repository-root `AGENTS.md` is
+> no longer part of the agent's prompt, so `.tau/SYSTEM.md` no longer calls it developer
+> guidance. `TAU_INCLUDE_DEVELOPMENT_RESOURCES` stays unset: the Analyst is not a coding
+> agent.
+>
 > Amendment (2026-10-22): `list_table_producers` lists a time-index table's registered
 > producers with `code_repository_branch_uid`, the branch the SDK declared when each was
 > first registered, or null (issue #89). Only `GET /meta-tables/{uid}/updates` adds that

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mainsequence-metatable"
-version = "0.1.58.dev89"
+version = "0.1.59.dev90"
 description = "Main Sequence MetaTables Python client and standalone API"
 readme = "README.md"
 requires-python = ">=3.13"
@@ -60,7 +60,7 @@ Documentation = "https://potential-doodle-wn39mnm.pages.github.io/"
 [project.optional-dependencies]
 dev = ["pytest>=8,<10", "ruff>=0.14", "build>=1,<2", "packaging>=24.2", "twine>=6,<7"]
 docs = ["mkdocs>=1.6,<2"]
-agent = ["ms-tau-sdk==2.0.18"]
+agent = ["ms-tau-sdk==2.0.26"]
 mysql = ["PyMySQL[rsa]>=1.1.1,<1.2"]
 # Keep the published extra name for existing installers; pyodbc is required.
 mssql = []

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/scripts/check_boundaries.py

@@ -44,7 +44,8 @@ PLATFORM_PATH = re.compile(r'/(?:orm/api|auth/jwt-token|api/v1/data[-_]sources)(
 
 def check(project: Path = PROJECT) -> list[str]:
     errors = []
-    roots = [project / root for root in ('api', 'src/metatables', 'docs', 'tests', '.agents/skills')]
+    roots = [project / root for root in ('api', 'src/metatables', 'docs', 'tests', '.agents/skills',
+                                         '.tau/skills/discover-tables', '.tau/skills/analyze-with-sql')]
     files = [project / 'README.md', project / 'pyproject.toml']
     files += [p for root in roots for p in root.rglob('*') if p.suffix in {'.py', '.md', '.json', '.toml'}]
     managed = project / '.agents/skills/ms_tau_sdk'  # Written by `ms-tau skills sync`, not by this repository.

{mainsequence_metatable-0.1.58.dev89 → mainsequence_metatable-0.1.59.dev90}/scripts/check_docs.py

@@ -16,6 +16,8 @@ def check(project: Path = PROJECT) -> list[str]:
     files += list((project / 'src/metatables/examples').rglob('*.md'))
     files += list((project / 'docs').rglob('*.md'))
     files += list((project / '.agents/skills').rglob('SKILL.md'))
+    # The Analyst's own skills; the vendored pg-aiguide skills beside them are upstream text.
+    files += [project / '.tau/skills' / name / 'SKILL.md' for name in ('discover-tables', 'analyze-with-sql')]
     errors = []
     for path in files:
         if not path.is_file(): continue