Phase 0 - Project Organization: - Create docs/PROJECT_STRUCTURE.md documenting codebase layout - Create markitect/core/ with parser, serializer, document_manager, workspace - Create markitect/schema/ consolidating 6 schema_*.py modules - Create markitect/storage/ with database module - Maintain backward compatibility via re-exports from original locations - Add docs/roadmap/information-space-service/ with README and WORKPLAN Phase 1 - Foundation (Weeks 1-3): - Week 1: Core domain models (InformationSpace, SpaceDocument, SpaceConfig, SpaceMetadata, SpaceVariable, TransclusionReference, SpaceStatus) - Week 2: Repository layer with interfaces (ISpaceRepository, IDocumentAssociationRepository, IVariableRepository, IReferenceRepository) and SQLite implementations with foreign key cascade deletes - Week 3: SpaceService orchestration layer with full CRUD, document, variable, and reference tracking operations Test coverage: 124 tests (25 model + 63 repository + 36 integration) Capabilities delivered: - CAP-001: InformationSpace entity with lifecycle management - CAP-002: SpaceRepository CRUD with SQLite backing - CAP-003: Document-Space associations with path-based organization - CAP-004: Space metadata and configuration schemas - CAP-005: Database schema with migrations Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
26 lines
575 B
Python
26 lines
575 B
Python
"""
|
|
Schema Analyzer - Backward Compatibility Module.
|
|
|
|
This module re-exports from markitect.schema.analyzer for backward compatibility.
|
|
New code should import from markitect.schema.analyzer directly.
|
|
"""
|
|
|
|
# Re-export from schema package for backward compatibility
|
|
from markitect.schema.analyzer import (
|
|
SchemaAnalyzer,
|
|
SchemaAnalysisResult,
|
|
SchemaIssue,
|
|
IssueType,
|
|
IssueSeverity,
|
|
analyze_schema_cli,
|
|
)
|
|
|
|
__all__ = [
|
|
'SchemaAnalyzer',
|
|
'SchemaAnalysisResult',
|
|
'SchemaIssue',
|
|
'IssueType',
|
|
'IssueSeverity',
|
|
'analyze_schema_cli',
|
|
]
|