1.1 Project Chronology & Decision Registry
This document serves as the official registry of system chronology, major architectural shifts, and definitive design decisions since the inception of the
@stndecosystem.
1. System Chronology
Q4 2025: Initial Research & Conceptualization
Research was initiated to optimize static document generation pipelines. Early design specifications conceptualized a parser-driven system capable of rendering Markdown sources into typeset pages. Standardizing vocabulary and core data structures was designated as a baseline requirement.
Q1 2026: Shift from Platform to Utility
Analysis of user friction models identified account registration as a primary bottleneck. The system architecture was pivoted from a platform-centric model to a zero-friction utility model. The primary objective became: anonymous document rendering under 10 seconds. User authentication was decoupled from basic rendering and refactored as an opt-in feature for persistent storage.
Q2 2026: Framework Modularization & Client Integration
Crystallization of the @stnd framework as a modular vertical-slice architecture. Implementation of the six system design presets (Temperaments) and the development of the local Obsidian integration client (obsidian-atelier), cementing the file-over-app storage paradigm.
Q3 2026: Integration Audit & Deployment
Execution of system-wide audits validating Edge deployment security boundaries, rate limiting, and anonymous storage lifecycle protocols. Release of the production-ready specification manual.
2. Architectural Decision Registry
| ID | Decision | Inception | Rationale |
|---|---|---|---|
ADR-001 |
Custom Modular Framework (@stnd on Astro + Cloudflare) |
Q4 2025 | Standardize the deployment stack and isolate core rendering logic from third-party vendor lock-in. |
ADR-002 |
System Lexicon Enforcement | Q4 2025 | Enforce standard terminology across code, database schemas, and documentation to prevent semantic drift. |
ADR-003 |
Anonymous-First Utility | Q1 2026 | Remove authentication barriers to maximize throughput and minimize user friction. |
ADR-004 |
Parallel Track Isolation | Q1 2026 | Separate the core specification (stnd.build) from product implementations (stnd.gd) to allow independent versioning. |
ADR-005 |
Pure Read-Only AI Integration | Q4 2025 | Restrict AI agents to reading and relational tasks (Mycelium network) with zero write permissions on user spaces. |
ADR-006 |
Deterministic Storage Expiry | Q4 2025 | Expire anonymous documents (Annuals) after a 7-day interval to prevent database bloat; persist authenticated documents indefinitely. |
ADR-007 |
Non-Algorithmic Interconnection | Q4 2025 | Rely exclusively on explicit backlinks and semantic citations for discovery, prohibiting feeds or engagement metrics. |
ADR-008 |
Passwordless Authentication | Q2 2026 | Mitigate credential-related security risks and user friction via email codes and passkey integrations. |
ADR-009 |
File-Over-App Paradigm | Q2 2026 | Design frontmatter as the primary configuration input. Ensure local Markdown files remain the immutable source of truth. |
ADR-010 |
Specification/Product Decoupling | Q2 2026 | Treat the Standard as an open specification (stnd.build) and standard.garden as a specific runtime implementation. |
3. System Invariants
Every modification to the @stnd ecosystem must comply with the following four invariants. Any proposal violating an invariant is rejected by default.
- Aesthetic Autonomy: Automated typesetting rules derived from mathematical grid constraints must be applied without exception.
- Latency Bound: The pipeline must execute from input to published URL in under 10 seconds.
- Data Independence: Source files must remain fully legible and structured in plain Markdown, independent of any proprietary runtime.
- Resource Constraints: Runtime execution must be optimized for minimal CPU time and zero cold starts at the Edge.
This registry is immutable once commited. Version updates must append new entries.