Docs

Reference knowledge base for the Localz project — an Obsidian vault of research, strategy, architecture, and product-definition notes. Unlike LocalzPlans/, LocalzDevelopements/, and LocalzChangeLogs/, this directory isn't tied to a release cycle: it's the "why" and "what" behind the product, kept around for as long as it's still true.

What belongs here

• Strategy, architecture, and tech-stack decisions (e.g. Localz-Strategy-and-Architecture-Note.md, Tech-Stack.md, Localz-Required-Stack.md, Anti-Lockin-Pattern-for-Startup-Stack.md)
• Requirements (Functional-Requirements.md, Non-functional-Requirements.md)
• Product/business analysis (Monetization-Plan.md, Competitors.md, Service-Based-Cost-Analysis.md, Data-Analysis-and-Insights.md, Cost-and-Value-Tracker.md)
• Service-type and persona definitions — the marketplace's offering/consumer models (One-time-Short-Service*.md, One-time-Long-Service*.md, Seasonal-Service*.md, Weekly-Subscription-Service*.md, Monthly-Subscription-Service*.md, Example-Persona.md)
• Roadmap and capacity notes (MVP-Development.md, MVP-to-Phase-2-Roadmap.md, Development-Setup-Resources-and-Capacity.md)

Rules

• Write notes as living documents — update them in place as understanding changes, rather than leaving stale versions behind.
• Once an idea here turns into committed work, it should be reflected as a plan in ../LocalzPlans/ (or directly as in-progress work in ../LocalzDevelopements/) — this directory stays the reference, not the tracker for active work.
• Prefer descriptive file names over version numbers or dates; these notes aren't scoped to a release.