[Story 2/3] Tutorial: Multi-Tenant Document Vault with FSM & Dual-Backend ObjectUri #9
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
qa:preview
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
quatrain/core#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🎯 Story Overview
As a B2B SaaS Tech Lead,
I want to build a secure, multi-tenant Document Vault featuring finite state machine approval workflows, dual-backend persistence (PostgreSQL for active data + SQLite for immutable audit logs), and Field-Level Security,
So that documents can be managed with full regulatory compliance and automated ObjectUri routing across distinct storage engines.
📦 Ecosystem Packages
@quatrain/core&@quatrain/state-machine(FSM, Workflow Transitions)@quatrain/backend,@quatrain/backend-postgres&@quatrain/backend-sqlite(Dual-Backend, ObjectUri Routing)@quatrain/auth&@quatrain/auth-rbac(Supabase/OIDC Auth, Field-Level Security)@quatrain/storage&@quatrain/storage-s3(S3StorageAdapter, Presigned URLs)📋 Child Tasks & Implementation Plan
feat(example-doc-vault): design document entity with state machine lifecyclefeat(example-doc-vault): implement dual-backend routing with automatic ObjectUri deductionfeat(example-doc-vault): configure Supabase Auth, RBAC Field-Level Security and S3 presigned storagedocs(example-doc-vault): write comprehensive step-by-step tutorial and README✅ Acceptance Criteria
DRAFT➔IN_REVIEW➔APPROVED➔ARCHIVED).repo.read('archive:audit_logs/log-505')automatically routes to the secondary SQLite backend without manual repository plumbing.financialAmount) for non-finance roles viasanitizeRead.examples/document-vault.