Scriptorium Architecture
Three-tier personal infrastructure for developing, deploying, and publishing intellectual tools.
The Domains
- labs-lab.com - Public identity and entrance
- scriptorium.online - Reusable toolkit platform
Key Insight
scriptorium.online inverts the typical “deploy my app” model. Instead of standalone applications, it provides composable services that any project can consume.
Not: “Here’s MY market app you can use”
But: “Here’s a MARKET SERVICE any project can consume”
Services as Toolkit
Current projects becoming services:
- Metatopic v3 - Semantic indexing as a service
- Prediction Markets Measure Information - Market infrastructure and widgets
- Wiki generators (planned)
- Text processing pipelines (planned)
Control Plane
~/system/ evolves from server management to orchestration:
- Deployment pipeline: ~/proj → local → Tailscale → scriptorium
- Service registry (what’s deployed where)
- Access tier promotion
- Health monitoring across all services
- Container coordination via Podman
Progressive Deployment
Local Dev → Working in ~/proj
Tailscale Internal → Private team access (Authentik OIDC)
Public (scriptorium.online) → Published tool APIs
Public (labs-lab.com) → Documentation layer
Philosophy
- Reusability - Build tools once, use in many projects
- Service-oriented - Everything exposed as APIs/MCPs
- Constraint-driven - Embrace limitations
- Type-safe infrastructure - PostgreSQL constraints, Pydantic schemas
- Emergent organization - Let structure emerge from use
Related: Budget Constraints Drive Emergence