[Story 2/3] Tutorial: Multi-Tenant Document Vault with FSM & Dual-Backend ObjectUri #9

Open
opened 2026-10-27 14:51:21 +00:00 by crapougnax · 0 comments
Owner

Migrated from GitHub https://github.com/Quatrain/Core/issues/36 (opened by @crapougnax on 2026-09-18).

🎯 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

  • #10: feat(example-doc-vault): design document entity with state machine lifecycle
  • #11: feat(example-doc-vault): implement dual-backend routing with automatic ObjectUri deduction
  • #12: feat(example-doc-vault): configure Supabase Auth, RBAC Field-Level Security and S3 presigned storage
  • #13: docs(example-doc-vault): write comprehensive step-by-step tutorial and README

✅ Acceptance Criteria

  1. Finite state machine enforces valid state transitions (DRAFT ➔ IN_REVIEW ➔ APPROVED ➔ ARCHIVED).
  2. repo.read('archive:audit_logs/log-505') automatically routes to the secondary SQLite backend without manual repository plumbing.
  3. Field-Level Security masks sensitive fields (financialAmount) for non-finance roles via sanitizeRead.
  4. S3 presigned upload/download URLs work against MinIO and AWS S3.
  5. Full runnable reference application under examples/document-vault.
> Migrated from GitHub https://github.com/Quatrain/Core/issues/36 (opened by @crapougnax on 2026-09-18). ## 🎯 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 - [ ] #10: `feat(example-doc-vault): design document entity with state machine lifecycle` - [ ] #11: `feat(example-doc-vault): implement dual-backend routing with automatic ObjectUri deduction` - [ ] #12: `feat(example-doc-vault): configure Supabase Auth, RBAC Field-Level Security and S3 presigned storage` - [ ] #13: `docs(example-doc-vault): write comprehensive step-by-step tutorial and README` --- ### ✅ Acceptance Criteria 1. Finite state machine enforces valid state transitions (`DRAFT` ➔ `IN_REVIEW` ➔ `APPROVED` ➔ `ARCHIVED`). 2. `repo.read('archive:audit_logs/log-505')` automatically routes to the secondary SQLite backend without manual repository plumbing. 3. Field-Level Security masks sensitive fields (`financialAmount`) for non-finance roles via `sanitizeRead`. 4. S3 presigned upload/download URLs work against MinIO and AWS S3. 5. Full runnable reference application under `examples/document-vault`.
Sign in to join this conversation.
No milestone
No project
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
quatrain/core#9
No description provided.