Mark/mesh-seed
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

META-006: Multi-Tenant Support #204

New issue
Closed
opened 2026-04-11 05:54:25 +00:00 by Mark · 3 comments
Mark commented 2026-04-11 05:54:25 +00:00
Owner
Copy link
No description provided.
Mark commented 2026-05-28 11:49:53 +00:00
Author
Owner
Copy link

⏸ Needs Decision

What needs to be decided?

  • Should this be split into smaller sub-issues? If yes, remove the blocked:needs-decision label and the triage will create a decomposition issue.
  • Do you want to proceed despite the risk? If yes, remove the blocked:needs-decision label and the triage will approve it.

Blocking factors:

  • Large scope — may need decomposition into phased sub-issues
  • High risk — needs human sign-off before proceeding

Scope: large Risk: high Spec: partial Type: feature
Summary: Introduce tenant isolation boundaries across the mesh substrate, including tenant-scoped ledger state, intent routing, worker execution isolation, and API-level authentication.
Suggestion: Decompose into phased sub-milestones: (1) tenant identity model + ledger scoping (new data model, schema migration), (2) tenant-aware routing + worker isolation (scoped intents, isolated exec contexts), (3) tenant API auth gateway, (4) isolation guarantee test suite. Each phase needs a security gate before proceeding to the next.
Rationale: SCOPE=large: touches 15+ files across ledger, routing, spawning, API gateway, backplane, config, and tests — a new cross-cutting identity layer. RISK=high: security-critical isolation boundaries, high blast radius if wrong, touches every core routing and execution path. SPEC=partial: the system's distributed mesh architecture naturally accommodates multi-tenancy, but it's absent from all existing docs, milestones, and current active work (M009). TYPE=feature: new major subsystem, not a fix or enhancement to existing functionality.

To unblock: Remove the blocked:needs-decision label. The triage will apply the appropriate outcome based on your choice above.

## ⏸ Needs Decision **What needs to be decided?** - **Should this be split into smaller sub-issues?** If yes, remove the `blocked:needs-decision` label and the triage will create a decomposition issue. - **Do you want to proceed despite the risk?** If yes, remove the `blocked:needs-decision` label and the triage will approve it. **Blocking factors:** - **Large scope** — may need decomposition into phased sub-issues - **High risk** — needs human sign-off before proceeding --- **Scope:** large **Risk:** high **Spec:** partial **Type:** feature **Summary:** Introduce tenant isolation boundaries across the mesh substrate, including tenant-scoped ledger state, intent routing, worker execution isolation, and API-level authentication. **Suggestion:** Decompose into phased sub-milestones: (1) tenant identity model + ledger scoping (new data model, schema migration), (2) tenant-aware routing + worker isolation (scoped intents, isolated exec contexts), (3) tenant API auth gateway, (4) isolation guarantee test suite. Each phase needs a security gate before proceeding to the next. **Rationale:** SCOPE=large: touches 15+ files across ledger, routing, spawning, API gateway, backplane, config, and tests — a new cross-cutting identity layer. RISK=high: security-critical isolation boundaries, high blast radius if wrong, touches every core routing and execution path. SPEC=partial: the system's distributed mesh architecture naturally accommodates multi-tenancy, but it's absent from all existing docs, milestones, and current active work (M009). TYPE=feature: new major subsystem, not a fix or enhancement to existing functionality. **To unblock:** Remove the `blocked:needs-decision` label. The triage will apply the appropriate outcome based on your choice above.
Mark commented 2026-08-14 02:47:42 +00:00
Author
Owner
Copy link

Mark — this issue needs scope before any work can be routed. The body is empty and the ledger-side core already landed on origin/master (f15a440 feat(#204)), but the remaining scope (tests + runtime/docker/cli tenant wiring) has no requirements to plan against.

Please confirm:

  1. Tenant isolation model: schema-per-tenant, db-per-tenant, or row-level?
  2. Auth/tenant-routing: subdomain, header, or JWT claim?
  3. Which surfaces must be multi-tenant first: API, UI, or data plane?

Once the body or this thread has those answers, the fixit lane can decompose and dispatch the remaining work.

Mark — this issue needs scope before any work can be routed. The body is empty and the ledger-side core already landed on origin/master (f15a440 feat(#204)), but the remaining scope (tests + runtime/docker/cli tenant wiring) has no requirements to plan against. Please confirm: 1. **Tenant isolation model**: schema-per-tenant, db-per-tenant, or row-level? 2. **Auth/tenant-routing**: subdomain, header, or JWT claim? 3. **Which surfaces must be multi-tenant first**: API, UI, or data plane? Once the body or this thread has those answers, the fixit lane can decompose and dispatch the remaining work.
Mark commented 2026-09-05 07:39:36 +00:00
Author
Owner
Copy link

Closing this as a stale empty body — core multi-tenant work landed in f15a440 feat(#204) on origin/master. The remaining scope (tests + runtime/docker/cli tenant wiring) has been split into a properly-spec'd followup: Mark/mesh-seed#285. The followup carries the three open scope questions (tenant isolation model, auth/tenant-routing, which surfaces first) as the acceptance gate before any code lands. Filing done via kilo-gsd-runner for Mark/mesh-seed#204 on 2026-09-04.

Closing this as a stale empty body — core multi-tenant work landed in `f15a440 feat(#204)` on origin/master. The remaining scope (tests + runtime/docker/cli tenant wiring) has been split into a properly-spec'd followup: **Mark/mesh-seed#285**. The followup carries the three open scope questions (tenant isolation model, auth/tenant-routing, which surfaces first) as the acceptance gate before any code lands. Filing done via kilo-gsd-runner for `Mark/mesh-seed#204` on 2026-09-04.
Mark closed this issue 2026-09-05 07:39:53 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
mesh-seed#142-gate-verify-pass-07b1f89
Labels
Clear labels   
blocked:children

   
blocked:commit-ready-failed

   
blocked:depends-231

Depends on #231 (Discord Bot Foundation) landing first. Do not pick until #231 is closed.

  
blocked:depends-236

Depends on #236 (Phase 1) landing first. Do not pick until #236 is closed.

  
blocked:depends-237

Depends on #237 (Phase 2) landing first. Do not pick until #237 is closed.

  
blocked:depends-238

Depends on #238 (Phase 3) landing first. Do not pick until #238 is closed.

  
blocked:depends-239

Depends on #239 (Phase 4) landing first. Do not pick until #239 is closed.

  
blocked:gate-fetch

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-research

   
blocked:needs-attention

Janitor escalated: pipeline terminated without producing expected changes. Human review required.

  
blocked:needs-decision

   
blocked:no-changes

   
blocked:no-procedure

   
blocked:preflight

Preflight check failed

  
blocked:verify-failed

   
bug

Something is broken

  
enhancement

New feature or request

  
feature-request

   
high-priority

Critical path items

  
in-progress

Issue is currently being worked on by a quickfix runner

  
lint-cleanup

Repo lint baseline is dirty

  
needs-decompose

   
needs-triage

   
ops-retry

   
ops-task

Operations task — install, configure, deploy, API calls

  
phase-5

Phase 5 Self-Building Infrastructure

  
quickfix

Pipe to opencode for direct fix

  
security/medium

Medium severity security issue

  
self-building

Autonomous code generation and self-improvement

  
triage-approved

Approved by triage — queued for fixer pipeline

No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/mesh-seed#204
No description provided.