Files
magnus919_agent-skills/multi-tenant-saas-architecture/references/source-index.md
T
Magnus HedemarkandGitHub 11381f89c3 feat: add multi-tenant SaaS architecture (#360)
Add tenant semantics, planes, tenancy models, lifecycle and commercial handoffs, operations, templates, evals, and specialist routing.\n\nAI-assisted: Jasper orchestrated implementation and verification with OpenCode.

Signed-off-by: Magnus Hedemark <magnus919@pm.me>
2026-08-21 03:13:16 -04:00

2.3 KiB

Source Index and Transformation Boundary

This skill is an original, task-centered synthesis. Public sources inform concepts and terminology; they are not copied as instructional text.

Public source Use in this skill URL
NIST SP 800-57 Part 1 Rev. 5 Key ownership and lifecycle questions that affect tenant data boundaries https://csrc.nist.gov/pubs/sp/800/57/pt1/r5/final
OWASP Application Security Verification Standard Boundary verification and authorization evidence as a security handoff https://github.com/OWASP/ASVS
OWASP API Security Top 10 Object/function authorization and resource-consumption risks to route to security/API owners https://owasp.org/API-Security/editions/2023/en/0x11-t10/
OpenID Connect Core 1.0 Identity-provider and relying-party terminology for onboarding handoffs https://openid.net/specs/openid-connect-core-1_0.html
RFC 7644 (SCIM Protocol) Provisioning and deprovisioning vocabulary for enterprise tenant lifecycle https://www.rfc-editor.org/rfc/rfc7644
W3C Trace Context Trace propagation context for tenant-aware observability handoffs https://www.w3.org/TR/trace-context/
Google SRE resources Reliability, failure, and operational evidence framing https://sre.google/sre-book/table-of-contents/
W3C Data Privacy Vocabulary Neutral vocabulary for data categories, purposes, and personal-data handling https://www.w3.org/TR/dpv/

Licensed-books boundary

The supplied private comparison report and purchased books may inform research only. This repository does not reproduce their prose, tables, diagrams, examples, taxonomies, chapter order, or distinctive presentation. The deliverable is organized around user tasks and repository ownership boundaries, with fresh examples, templates, and eval fixtures. No purchased ebook is a source file for this skill and no purchased ebook should be read or quoted when using it.

Provenance and review

  • Research input: the safe synthesized architecture comparison supplied for this task.
  • Transformation: public sources, issue requirements, and existing specialist boundaries were compared, then rewritten as original procedures and artifacts.
  • Review rule: if a future edit resembles a source's distinctive expression or structure, rewrite it from the user task and re-check this boundary before publication.