How johnandrewbalbarosa/neoterritory works
NeoTerritory is a research-oriented learning product whose central workflow analyzes submitted C++ projects for design-pattern evidence and presents source-anchored educational reports. The documented analyzer stages run from source reading through tree construction, pattern dispatch, evidence linking, and report generation. Separate learning and administration branches provide assessments, readiness decisions, saved-run review, and operational controls. The README describes the service boundaries and the C++ pipeline contract declares its stages; sampled excerpts do not establish every runtime connection between them.
Main entry points: pipeline_state.hpp Pipeline contract · projectLearningOrchestrationController.ts Learning controller · client.ts Frontend API client · algorithm_pipeline.hpp Analysis report
Components 22
C++ Analysis
- Pipeline contract
Codebase/Microservice/Modules/Header/OutputGeneration/Contracts/pipeline_state.hpp - Read source
Codebase/Microservice/Modules/Header/Analysis/Input/source_reader.hpp - Build trees
Codebase/Microservice/Modules/Header/OutputGeneration/Contracts/pipeline_state.hpp - Match patterns
Codebase/Microservice/Modules/Header/Analysis/Patterns/Catalog/matcher.hpp - Link evidence
Codebase/Microservice/Modules/Header/HashingMechanism/HashLinks/Flow/parse_tree_hash_links_program_flow.hpp - Analysis report
Codebase/Microservice/Modules/Header/OutputGeneration/Contracts/algorithm_pipeline.hpp
API Services
- Backend API
Codebase/Backend/server.ts - Transform routes
Codebase/Backend/src/routes/transform.ts - Transform controller
Codebase/Backend/src/controllers/transformController.ts
Learning
- Project learning routes
Codebase/Backend/src/routes/projectLearningOrchestration.ts - Learning controller
Codebase/Backend/src/controllers/projectLearningOrchestrationController.ts - Project brief intake
Codebase/Backend/src/services/projectSpecIntakeService.ts - Feature toggle policy
Codebase/Backend/src/services/featureTogglePolicyService.ts - Assessment scoring
Codebase/Backend/src/services/assessmentOrchestrationService.ts - Readiness evidence
Codebase/Backend/src/services/readinessEvidenceService.ts
User Interfaces
- Studio submission
Codebase/Frontend/src/components/studio/StudioApp.tsx - Frontend API client
Codebase/Frontend/src/api/client.ts - Annotated results
Codebase/Frontend/src/components/analysis/SourceView.tsx - Learning assessments
Codebase/Frontend/src/components/learn/LearningAssessmentPage.tsx - Admin console
Codebase/Frontend/src/admin/AdminApp.tsx - Saved run controls
Codebase/Frontend/src/admin/components/RunsManager.tsx
Other components
- Student or researcher
Connections 21
- Student or researcher → Studio submission: submits C++
- Studio submission → Frontend API client: sends request
- Frontend API client → Backend API: calls API
- Backend API → Transform routes: dispatches
- Transform routes → Transform controller: routes to
- Transform controller → Pipeline contract: invokes analysis
- Pipeline contract → Read source: runs stage
- Pipeline contract → Build trees: runs stage
- Pipeline contract → Match patterns: runs stage
- Pipeline contract → Link evidence: runs stage
- Pipeline contract → Analysis report: generates
- Analysis report → Annotated results: returns findings
- Student or researcher → Learning assessments: takes assessments
- Learning assessments → Project learning routes: submits attempt
- Project learning routes → Learning controller: routes to
- Learning controller → Project brief intake: intakes brief
- Learning controller → Feature toggle policy: resolves toggles
- Learning controller → Assessment scoring: scores attempt
- Learning controller → Readiness evidence: checks readiness
- Admin console → Frontend API client: calls API
- Saved run controls → Frontend API client: loads and manages runs