Restructure documentation for independent protocol website

- Move planning docs to /internal/planning/
- Consolidate technical docs from /docs/ into /content/docs/
- Add new sections: architecture, standards, migration
- Create index pages for new sections
- Update all cross-references to new paths
- Remove redundant /docs/ directory

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Author: Copilot

.github/prompts/README.md

@@ -292,8 +292,8 @@ When designing protocols, benchmark against:
 
 ### Repository Documentation
 - [ARCHITECTURE.md](../../ARCHITECTURE.md) - System architecture
-- [DEVELOPMENT_ROADMAP.md](../../DEVELOPMENT_ROADMAP.md) - Development plan
-- [PRIORITIES.md](../../PRIORITIES.md) - Priority matrix
+- [DEVELOPMENT_ROADMAP.md](../../internal/planning/DEVELOPMENT_ROADMAP.md) - Development plan
+- [PRIORITIES.md](../../internal/planning/PRIORITIES.md) - Priority matrix
 - [README.md](../../README.md) - Project overview
 
 ### Protocol Documentation

ARCHITECTURE.md

@@ -474,6 +474,6 @@ Same Protocol → Different Renderers:
 ---
 
 **For more details, see:**
-- [DEVELOPMENT_ROADMAP.md](./DEVELOPMENT_ROADMAP.md) - Complete development plan
-- [PRIORITIES.md](./PRIORITIES.md) - What to work on next
+- [DEVELOPMENT_ROADMAP.md](./internal/planning/DEVELOPMENT_ROADMAP.md) - Complete development plan
+- [PRIORITIES.md](./internal/planning/PRIORITIES.md) - What to work on next
 - [packages/spec/README.md](./packages/spec/README.md) - Technical documentation

CONTRIBUTING.md

@@ -52,8 +52,8 @@ pnpm test
 ### 1. Choose What to Work On
 
 Before starting, review:
-- **[PRIORITIES.md](./PRIORITIES.md)** - Current sprint priorities
-- **[DEVELOPMENT_ROADMAP.md](./DEVELOPMENT_ROADMAP.md)** - Long-term roadmap
+- **[PRIORITIES.md](./internal/planning/PRIORITIES.md)** - Current sprint priorities
+- **[DEVELOPMENT_ROADMAP.md](./internal/planning/DEVELOPMENT_ROADMAP.md)** - Long-term roadmap
 - **[GitHub Issues](https://github.com/objectstack-ai/spec/issues)** - Open issues
 
 ### 2. Create a Branch
@@ -406,7 +406,7 @@ Brief description of changes
 
 ### Getting Help
 
-- Review [PLANNING_INDEX.md](./PLANNING_INDEX.md) for documentation navigation
+- Review [PLANNING_INDEX.md](./internal/planning/PLANNING_INDEX.md) for documentation navigation
 - Check [ARCHITECTURE.md](./ARCHITECTURE.md) for system design
 - Read [QUICK_START_IMPLEMENTATION.md](./QUICK_START_IMPLEMENTATION.md) for implementation examples
 

README.md

@@ -15,29 +15,29 @@ This repository contains the core specifications, schemas, and protocols that po
 *   **[Installation Guide](./content/docs/guides/installation.mdx):** Setup instructions
 *   **[Contributing Guide](./CONTRIBUTING.md):** How to contribute to the project
 
-### Planning & Architecture
-*   **[Development Roadmap](./DEVELOPMENT_ROADMAP.md):** Complete development plan considering all future possibilities
-*   **[Priority Matrix](./PRIORITIES.md):** What to work on next, sprint planning guide
-*   **[Architecture Diagrams](./ARCHITECTURE.md):** Visual reference for the complete system
-*   **[Planning Index](./PLANNING_INDEX.md):** Complete guide to navigating planning documentation
+### Architecture & Design
+*   **[Architecture Overview](./content/docs/architecture/):** Deep dive into the three-layer architecture
+*   **[Data Layer (ObjectQL)](./content/docs/architecture/data-layer.mdx):** Query language and data abstraction
+*   **[UI Layer (ObjectUI)](./content/docs/architecture/ui-layer.mdx):** Server-driven UI protocol
+*   **[System Layer (ObjectOS)](./content/docs/architecture/system-layer.mdx):** Runtime kernel and plugins
 
-### Technical Documentation
+### Standards & Best Practices
+*   **[Naming Conventions](./content/docs/standards/naming-conventions.mdx):** Schema naming rules (camelCase vs snake_case)
+*   **[API Design](./content/docs/standards/api-design.mdx):** API design principles and patterns
+*   **[Error Handling](./content/docs/standards/error-handling.mdx):** Consistent error handling strategies
+*   **[Authentication](./content/docs/standards/authentication.mdx):** Authentication standards and implementation
+
+### Documentation Site
 The official documentation is built with Fumadocs and Next.js.
 
 *   **[Documentation Content](./content/docs/):** MDX documentation files (concepts, specifications, references)
 *   **[Documentation Site](./apps/docs/):** Fumadocs-powered Next.js app
-*   **[Technical Guides](./docs/):** In-depth technical guides and standards
 *   **[Live Site](http://localhost:3000/docs):** Run `pnpm docs:dev` to view locally
 
-### Architecture Deep Dives
-*   **[Data Layer (ObjectQL)](./docs/architecture/data-layer.md):** Query language and data abstraction
-*   **[UI Layer (ObjectUI)](./docs/architecture/ui-layer.md):** Server-driven UI protocol
-*   **[System Layer (ObjectOS)](./docs/architecture/system-layer.md):** Runtime kernel and plugins
-
-### Standards & Best Practices
-*   **[Naming Conventions](./docs/standards/naming-conventions.md):** Schema naming rules (camelCase vs snake_case)
-*   **[API Design](./docs/standards/api-design.md):** API design principles and patterns
-*   **[Error Handling](./docs/standards/error-handling.md):** Consistent error handling strategies
+### Planning & Internal Docs
+*   **[Development Roadmap](./internal/planning/DEVELOPMENT_ROADMAP.md):** Complete development plan
+*   **[Priority Matrix](./internal/planning/PRIORITIES.md):** What to work on next, sprint planning guide
+*   **[Planning Index](./internal/planning/PLANNING_INDEX.md):** Complete guide to navigating planning documentation
 
 ## 📦 Monorepo Structure
 
@@ -128,7 +128,7 @@ We welcome contributions! Please read our **[Contributing Guide](./CONTRIBUTING.
 ### Quick Start for Contributors
 
 1.  **Read the Docs**: Review [CONTRIBUTING.md](./CONTRIBUTING.md) for complete guidelines
-2.  **Check Priorities**: See [PRIORITIES.md](./PRIORITIES.md) for what to work on next
+2.  **Check Priorities**: See [PRIORITIES.md](./internal/planning/PRIORITIES.md) for what to work on next
 3.  **Understand Architecture**: Read [ARCHITECTURE.md](./ARCHITECTURE.md) for system overview
 4.  **Follow Standards**: Review [docs/standards/](./docs/standards/) for coding standards
 

RELEASE_NOTES.md

@@ -83,7 +83,7 @@ Version tag `v0.2.0` has been created for this release.
 ## 📚 Documentation
 
 Full documentation is available at:
-- Development Roadmap: [DEVELOPMENT_ROADMAP.md](DEVELOPMENT_ROADMAP.md)
+- Development Roadmap: [DEVELOPMENT_ROADMAP.md](internal/planning/DEVELOPMENT_ROADMAP.md)
 - Architecture: [ARCHITECTURE.md](ARCHITECTURE.md)
 - Quick Start: [QUICK_START_IMPLEMENTATION.md](QUICK_START_IMPLEMENTATION.md)
 

docs/architecture/data-layer.md content/docs/architecture/data-layer.mdxdocs/architecture/data-layer.md renamed to content/docs/architecture/data-layer.mdx

@@ -0,0 +1,38 @@
+---
+title: Architecture
+description: Deep dive into the ObjectStack Protocol Architecture
+---
+
+# Architecture
+
+The ObjectStack Protocol is built on three core layers that work together to provide a complete metadata-driven platform.
+
+## Core Layers
+
+### [Data Layer (ObjectQL)](/docs/architecture/data-layer)
+The Data Layer defines the "Shape of Data" and business logic. It includes:
+- **Schema**: Objects and Fields with 23+ field types
+- **Logic**: Workflows, Triggers, Validation Rules, Formulas
+- **Security**: Permissions and Sharing Rules
+- **Query**: Abstract Syntax Tree (AST) for unified data access
+
+### [UI Layer (ObjectUI)](/docs/architecture/ui-layer)
+The UI Layer defines the "Shape of Interaction" for rendering interfaces:
+- **Views**: Grid, Kanban, Calendar, Gantt, List configurations
+- **Pages**: FlexiPage layouts with regions and components
+- **Navigation**: App menus and navigation structures
+- **Analytics**: Reports and Dashboards with widgets
+
+### [System Layer (ObjectOS)](/docs/architecture/system-layer)
+The System Layer defines the "Runtime Environment":
+- **Manifest**: Application packaging
+- **Identity**: Authentication, Roles, Licenses
+- **Integration**: Webhooks, API contracts, ETL Mappings
+- **Datasource**: Driver definitions for SQL, NoSQL, SaaS connectors
+
+## Design Principles
+
+1. **Data as Code**: All configurations are expressed as declarative metadata
+2. **Intent over Implementation**: Describe what you want, not how to build it
+3. **Local-First**: Works offline, syncs when connected
+4. **Driver Agnostic**: Abstract away storage implementation details

content/docs/architecture/index.mdx

@@ -0,0 +1,9 @@
+{
+  "title": "Architecture",
+  "pages": [
+    "index",
+    "data-layer",
+    "ui-layer",
+    "system-layer"
+  ]
+}