Admin Database Schema Extensions

Relevant source files

The following files were used as context for generating this wiki page:

• README.md
• docs/PLAN.md
• CLAUDE.md
• upstream/inkweave
• vercel.json

Admin Database Schema Extensions refer to the architectural method by which the inkweave-admin project implements private administrative functionality on top of the base Inkweave application. This system allows for the management of internal data and user activities by extending the core application capabilities while maintaining a separation between public features and private administrative tools.

The extensions operate by pinning the public application as a submodule and deploying a specialized instance that incorporates administrative logic. Access to these extensions is restricted via platform-level authentication to ensure data security.

Sources: README.md:3-4, README.md:7

Submodule Integration and Core Extension

The project manages its relationship with the base application by pinning the core repository. This allows the admin system to inherit the primary database schema and application logic while providing a dedicated space for administrative extensions.

• Submodule Reference: The project maps the public Doberjohn/inkweave repository to the local path upstream/inkweave.
• Version Control: Administrative extensions depend on specific commits pinned within the submodule structure to ensure compatibility between the admin tools and the core schema.

The diagram above illustrates how the admin project wraps the public core repository to create a private extension layer.
Sources: README.md:3-4

Deployment and Security Architecture

The schema extensions and administrative tools are deployed as a discrete project. Security is enforced at the infrastructure level rather than just the application layer.

• Deployment Target: The system deploys to a specific Vercel project.
• Authentication Layer: Every administrative extension is protected by Vercel login, preventing public access to the admin database views and management functions.
• Configuration Management: Guidelines for interacting with this environment are defined in the CLAUDE.md and docs/PLAN.md files.

Component	Path / Location	Purpose
Core Submodule	upstream/inkweave	Provides the base database schema and application code.
Admin Tools	Root directory	Contains private extensions and administrative interfaces.
Project Plan	docs/PLAN.md	Tracks design, planning, and implementation phases of extensions.
Working Rules	CLAUDE.md	Defines development rules for the admin environment.

Sources: README.md:3-4, README.md:6-7

Extension Implementation Workflow

The process of extending the database or application for administrative use follows a structured phase-based approach. The actor (developer) follows the rules set in the documentation to modify or add administrative capabilities.

1. Refer to docs/PLAN.md for current phase status and design requirements.
2. Update the upstream/inkweave submodule if core schema changes are required.
3. Implement administrative logic within the inkweave-admin repository to wrap or extend core functions.
4. Deploy changes to the Vercel project to verify the extensions behind the secure login.

Sources: README.md:4, README.md:6-7

The Admin Database Schema Extensions system ensures that sensitive administrative capabilities remain decoupled from the public-facing Inkweave application. By utilizing git submodules and infrastructure-level authentication, the project maintains a secure and maintainable extension layer for internal platform management.