Campus Curriculum Optimization & Mapping Platform
COMPASS Guided Operations Hub
One organized path for course-level concept analysis, program review, curriculum mapping, transfer evaluation, documentation, and formal assurance materials.
Credits & Acknowledgement
COMPASS Project Team
Dr. Vignon Oussa
Developed and maintains COMPASS and its public documentation framework.
Dr. Uma Shama
Contributed strategic alignment, communication framing, and coauthorship of the Transfer Protocols framework.
Chigo Adigwe
Contributed workflow requirements and usability feedback.
Lalitha Bhavanand
Contributed implementation feedback and documentation refinement.
Nicole Medeiros
Contributed to COMPASS documentation and project deliverables.
Grant support: This work is supported by Bridgewater State University’s Academic Innovation Fund (InnovateBSU), Academic Innovation Project Grant (AY 2025–2026), for Leveraging AI for Curriculum Mapping and Analytics to Enhance Academic Foundations at BSU.
Orientation
COMPASS is a discipline-adaptable curriculum analytics platform for curriculum review, advising, program analysis, assessment, and transfer evaluation. Mathematics examples serve as templates rather than constraints. In every discipline, courses can be modeled as graph nodes, course relationships as edges, and course-level concepts, skills, outcomes, or competencies as another connected layer.
Course layer
Represent concepts as nodes and direct dependencies as edges. Save the concept list, matrix, analytics, and graph.
Program layer
Represent courses as nodes and prerequisite/corequisite relationships as edges. Inspect entry points, hubs, chains, and destinations.
Cross-course layer
Record where canonical concepts are introduced, developed, and mastered, then connect the map to transfer and assessment questions.
Which tool should I use?
| Your question | Start with | Save this output |
|---|---|---|
| What is happening inside one course? | Concept Analyzer | Concept list, dependency matrix, analytics, graph, and bottleneck summary. |
| How does the program pathway fit together? | Program Analyzer | Course graph, role classification, pathway questions, and exported visual. |
| Where do concepts appear across courses? | Curriculum Mapper | I/D/M matrix, progression narrative, and gap/redundancy notes. |
| Does an incoming course match a local course? | Course Transfer Analyzer | Mapping table, ranked candidates, diagnostics, and an auditable human-reviewed recommendation. |
| Which files, templates, or certificates do I need? | Documentation & Lean | Versioned inputs, templates, formal scope notes, and supporting archives. |
Standard two-pass operating sequence
Prepare
Confirm the source files, labels, coding conventions, privacy, date, and version.
Run static app
Build the matrix, graph, state file, curriculum map, or transfer evidence.
Export
Save the workbook, CSV, graph, or report with a stable name and version.
Use AI
Ask the matching assistant for Findings, Evidence, and Next Steps grounded in the export.
Review & archive
Apply faculty and policy judgment, then keep the final report with its supporting artifacts.
Department onboarding sequence
| Phase | Department action | Output |
|---|---|---|
| Prepare | Choose one program or concentration and appoint a small working group. | Course inventory, prerequisite/corequisite list, and shared folder for syllabi and outcomes. |
| Pilot | Analyze 2–4 strategically important courses. | Concept lists, dependency matrices, and early graph evidence. |
| Expand | Build the program graph and reconcile a shared vocabulary. | Program map, canonical concept/outcome list, and draft curriculum-map CSV. |
| Review | Use the AI assistants to interpret artifacts and draft the narrative. | Findings, Evidence, Next Steps; advising notes; transfer rationale. |
| Institutionalize | Assign update responsibility and version control. | Dated exports, stable file names, and a repeatable assessment cycle. |
Role-based starting points
- Department chair or program coordinator: begin with Program Analyzer and Curriculum Map.
- Faculty member: begin with Concept Analyzer for courses you teach.
- Assessment coordinator: use Curriculum Map to connect concepts and outcomes to evidence.
- Advisor: use Program Analyzer to explain sequencing, gateways, and preparation needs.
- Transfer evaluator: use Course Transfer Analyzer with a current map and complete incoming syllabus.
- Administrative or student assistant: maintain names, versions, exports, and folders; curricular interpretation remains with faculty.
First 30 minutes
| Time | Action | Expected result |
|---|---|---|
| 0–5 min | Review the four core modules and choose one component. | A clear starting point. |
| 5–10 min | Open the documentation for the selected component. | Required inputs and common mistakes are understood. |
| 10–18 min | Run a small static-app example. | One structured artifact. |
| 18–25 min | Export the artifact and open the corresponding AI assistant. | An evidence-grounded interpretation. |
| 25–30 min | Write three bullets: Findings, Evidence, Next Steps. | A committee-ready note for review. |
Quick access
BSU ChatGPT access
Request or confirm access before opening COMPASS AI assistants.
Open the BSU access request dashboardStatic analysis
Load course and state data, inspect the graph, classify course roles, review long chains, and export visuals. The tool is fully usable in this mode.
AI-enhanced analysis
Upload the exported graph or state file to identify patterns, frame faculty-review questions, and draft Findings, Evidence, and Next Steps. The AI strengthens interpretation and documentation.
Required inputs
| Input | Practical guidance |
|---|---|
| Course list | Include every course in the pathway being analyzed. |
| Edges | Enter prerequisite and corequisite relationships accurately. |
| State JSON / ZIP | Load the appropriate program state file when available. |
| Optional outcomes | Use DWF or other outcome signals only as prompts for inquiry. |
| Metadata | Keep course titles, terms offered, notes, and edge descriptions current. |
Five-minute workflow
- Open the Program Analyzer static app or the Program Map from the instructions page.
- Load the appropriate state file or dataset.
- Inspect the program graph and identify entry, feeder, hub, and terminal courses.
- Review long chains, high-reach courses, missing metadata, and advising-sensitive points.
- Export the graph and edge evidence, then use the AI assistant for review questions and narrative drafting.
How to read the output
| Signal | Interpretation |
|---|---|
| Entry course | A starting point where readiness and placement matter. |
| Hub course | A course with many downstream effects; alignment and support are important. |
| Terminal course | A course near the end of a pathway; it may indicate culmination. |
| Long chain | A sequence where one delay may postpone several later courses. |
| High downstream reach | Disruption may propagate quickly through the pathway. |
| Outcome flag | A question for review, not a final explanation. |
Recommended practices
- Use entry, feeder, hub, and terminal role labels.
- Separate structure from performance signals.
- Check metadata and missing courses before interpreting.
- Export a readable graph and a separate edge table.
- Name every state file and report by version and date.
Common pitfalls
- Drawing too many arrows on one figure.
- Treating a high-risk flag as a final explanation.
- Ignoring corequisites or concurrent-enrollment rules.
- Using placeholder course titles in reports.
- Making operational decisions without local context.
Recommended AI prompt
I have uploaded a program graph or state file. Identify entry courses, hubs, long chains, high-reach courses, and questions for faculty review. Treat outcome indicators as inquiry signals, not final judgments. Organize the response as Findings, Evidence, Next Steps.
Program review note template
| Program | Degree, concentration, catalog year, reviewer, and date/version. |
|---|---|
| Findings | Entry points, hubs, long chains, terminal destinations, and metadata concerns. |
| Evidence | Program graph, edge list, state-file version, and validated outcome summaries. |
| Next Steps | Faculty review, advising adjustment, metadata cleanup, assessment discussion, or pathway-redesign question. |
Program Analyzer resources
Static Program Analyzer
Open Program AnalyzerProgram Analyzer AI
Open Program Analyzer AI assistantAlignment instructions
Open Program Map Alignment instructionsProgram state files
Download program state files ZIPExample report
Open Program Analyzer example reportDepartment union example
Open department union exampleBuild the course model
Create a canonical concept list and mark direct dependencies using the accepted matrix values. Inspect the graph and export the matrix, analytics, and visualization.
Interpret the model
Use the exported matrix and graph to identify gateways, bottlenecks, dense or sparse regions, sequencing questions, and practical next steps.
Inputs and matrix convention
Inputs
- Short, canonical concept labels.
- Optional short descriptions.
- Direct prerequisite or support judgments.
- Course title, reviewer, date, and version.
Matrix values
- 1: direct prerequisite/support relation.
- 0: no direct relation.
- 0.5: genuine co-dependence only.
- ? unresolved relation requiring faculty judgment.
Five-minute workflow
- Open the Concept Analyzer and enter or import the canonical concept list.
- Mark only direct relationships; use ? where faculty judgment is unresolved.
- Inspect the matrix, graph, analytics table, cycles, reachability, and bottleneck indicators.
- Export the matrix and graph with the course, version, and date.
- Use the AI assistant to draft Findings, Evidence, and Next Steps grounded in the export.
How to read the output
| Signal | Interpretation |
|---|---|
| High outgoing reach | A possible gateway concept supporting many later concepts. |
| High incoming dependence | A concept that relies on substantial prior preparation. |
| Cycle | A strict linear teaching order cannot satisfy every stated dependency; review the judgments or teach a block jointly. |
| Bottleneck indicator | Weakness in the concept may disrupt learning across the course. |
| Dense graph | Recheck whether edges represent direct dependencies rather than topic adjacency. |
| Sparse graph | Recheck whether important direct prerequisites were omitted. |
Recommended practices
- Use short, canonical labels.
- Document assumptions with short descriptions.
- Mark only direct conceptual dependencies.
- Use ? when faculty judgment is needed.
- Reconcile matrices across instructors when possible.
Common pitfalls
- Duplicating one concept under different names.
- Marking all related topics as dependencies.
- Treating graph metrics as final judgments.
- Using 0.5 without genuine co-dependence.
- Exporting without a version and date.
Recommended AI prompt
I have uploaded a concept dependency matrix for [COURSE]. Identify the main gateway concepts, bottlenecks, sequencing concerns, and practical next steps. Cite the matrix, analytics table, or graph evidence and use the format: Findings, Evidence, Next Steps.
Minimal course-analysis report
| Course | Course code, title, instructor or reviewer, date, and version. |
|---|---|
| Concept set | Canonical concept labels and short descriptions. |
| Findings | Gateway concepts, bottlenecks, dense/sparse areas, and sequencing concerns. |
| Evidence | Dependency matrix, analytics export, graph, and faculty notes. |
| Next Steps | Scaffolding, diagnostic checks, sequencing changes, or faculty review items. |
Concept Analyzer resources
Static Concept Analyzer
Open Concept AnalyzerConcept Analyzer AI
Open Concept Analyzer AI assistantWritten guide
Open Concept Analyzer written guideVideo tutorial
Open Concept Dependency Matrix tutorialBuild the coverage matrix
Enter canonical concepts by row, courses by column, and only 0, 1, 2, or 3 as coverage values. Export a versioned CSV or workbook.
Interpret progression
Ask the AI assistant to locate healthy progressions, missing mastery, sudden mastery, repeated introduction, and likely gaps without inventing concepts.
I/D/M matrix convention
0 — Not taught
The course does not introduce or assess the concept.
1 — Introduced
Students receive an initial exposure to the concept.
2 — Developed
Students practice and strengthen the concept.
3 — Mastered
Students are expected to command the concept fluently and independently.
Five-minute workflow
- Open the Curriculum Mapper static app.
- Load or enter the concept-by-course matrix.
- Confirm that the concept column, course columns, and 0/1/2/3 values are clean.
- Review I/D/M patterns for each concept.
- Export the map and use the AI assistant to summarize gaps, redundancies, and progression concerns.
Curriculum-map reading patterns
| Pattern | Interpretation |
|---|---|
| 0, 1, 2, 3 | Healthy progression from introduction to mastery. |
| 1, 1, 1, 0 | Repeated introduction without visible development. |
| 0, 0, 0, 3 | Sudden mastery; preparation may be missing from the map. |
| 1, 2, 2, 0 | The concept is developed but not clearly mastered. |
| 0 across all courses | A possible gap, intentional omission, or concept that does not belong in the pathway. |
| 3 in many courses | Mastery may be overclaimed or inconsistently defined. |
Recommended practices
- Use a nonredundant canonical concept list.
- Base 0/1/2/3 assignments on evidence.
- Separate gaps from intentional omissions.
- Review suspicious patterns with faculty.
- Export a versioned CSV or workbook.
Common pitfalls
- Treating every topic as a separate row.
- Keeping synonyms as separate concepts.
- Assigning 3 without evidence of mastery.
- Allowing AI to invent missing labels.
- Changing the map without version control.
Recommended AI prompt
I have uploaded a curriculum map with 0/1/2/3 values. Identify healthy I/D/M progressions, missing mastery, sudden mastery, redundancy without progression, and likely gaps. Do not invent concepts. Cite the relevant rows and courses and summarize the result as Findings, Evidence, Next Steps.
Curriculum-map documentation template
| Scope | Program/pathway, courses included, catalog year, reviewers, date, and version. |
|---|---|
| Findings | Healthy progressions, repeated introduction, missing or sudden mastery, gaps, and redundancies. |
| Evidence | Versioned matrix, syllabi, assignments, outcomes, and faculty-review notes. |
| Next Steps | Faculty reconciliation, evidence review, feasible rebalancing, or explicit documentation of intentional omissions. |
Curriculum Map resources
Static Curriculum Mapper
Open Curriculum MapperCurriculum Mapping AI
Open Curriculum Mapping AI assistantCurriculum map data
Download curriculum map data ZIPTutorial video
Open Curriculum Mapper tutorialSample coverage CSV
Open sample coverage CSVPrepare the inputs
Use the current curriculum-map CSV, a complete incoming syllabus, and the local review context. Auditable matching requires an agreed local concept list.
Map and diagnose
Use the Transfer Analyzer to classify exact, near, and unmapped content; compute ranked evidence; and draft a recommendation that remains subject to faculty and policy review.
Required inputs
| Input | Must include |
|---|---|
| Curriculum map CSV | A canonical concept column; one column per local course; only 0, 1, 2, or 3 as coverage values. |
| Incoming syllabus | Complete title, description, learning outcomes, topics, schedule, assessments, and textbook/sections when available. |
| Review context | Receiving department, target local course if known, and whether strict mapping is required. |
Five-minute workflow
- Open the COMPASS Transfer Analyzer.
- Upload the official, current curriculum-map CSV.
- Paste or upload the complete incoming syllabus.
- Request concept mapping, overlap and weighted scores, ranked candidate courses, and diagnostics.
- Review exact, near, and unmapped matches, missing local concepts, extra topics, ties, confidence, and the proposed recommendation.
Scoring notation
Let (L) be the official concept list, (A\subseteq L) the mapped incoming concepts, and (X_Y\subseteq L) the concepts taught in local course (Y). The overlap score is
When a tie requires additional evidence, use the curriculum-map levels:
Every strongest match, including ties, should be reported. Unmapped or invented concepts must not be counted in the score.
Transfer output checklist
| Output section | Required content |
|---|---|
| Executive summary | Recommended equivalency, confidence, and reason. |
| Mapping table | Syllabus phrase, matched concept, exact/near/unmapped status, and justification. |
| Ranked courses | Each local course with overlap score (s(Y)), weighted score (w(Y)), and all ties. |
| Diagnostics | Missing concepts, extra concepts, coverage profile, and concerns. |
| Recommendation | Strong match, conditional match, partial match, no clear match, or human review. |
Recommended practices
- Use the official, current curriculum map.
- Provide the complete incoming syllabus.
- Distinguish exact, near, and unmapped topics.
- Use strict mode for high-stakes articulation.
- Save the report and inputs for audit.
Common pitfalls
- Deciding equivalency from title alone.
- Counting unmapped or invented concepts.
- Accepting near matches without explanation.
- Ignoring missing mastery-level concepts.
- Treating AI output as the final decision.
Recommended AI prompt
I have uploaded the official curriculum map and an incoming syllabus. Map syllabus topics to official concepts; separate exact, near, and unmapped matches; compute s(Y) and w(Y); rank candidate courses; report all ties; and provide an auditable recommendation with diagnostics. Do not count invented or unmapped concepts.
Transfer review note template
| Incoming course | Institution, course number, title, credits, syllabus date, and reviewer. |
|---|---|
| Local target | Candidate local course or pathway requirement. |
| Findings | Exact matches, near matches, unmapped topics, missing local concepts, and extra topics. |
| Evidence | Curriculum-map CSV, syllabus, mapping table, ranked scores, ties, and diagnostics. |
| Recommendation | Strong match, conditional match, partial match, no clear match, or human review. |
Course Transfer resources
COMPASS Transfer Analyzer
Open COMPASS Transfer AnalyzerTransfer tutorial
Open Transfer GPT tutorialTransfer protocol paper
Open Transfer Protocols paperTutorial curriculum map
Open tutorial curriculum map CSVTutorial syllabus
Open tutorial syllabus PDFStart Here documentation directory
Begin with documentation, produce a structured artifact, and then use the matching AI assistant to prepare review-ready documentation. Critical links are shown below with descriptive labels and visible URLs.
Orientation and ChatGPT access
Downloads, data, tutorials, and formal archives
Curriculum Mapper tutorial
Video walkthrough for the curriculum-map workflow.
Open Curriculum Mapper tutorialConcept Lean archive
Formal Lean 4/Mathlib companion archive for Concept Analyzer mathematics.
Open Concept Analyzer Lean archiveProgram Lean package
Formal core and independent audit materials; theorem hypotheses and scope qualifications apply.
Open Program Analyzer Lean packageTransfer certification
Certificate, independent review, evidence, and a precise statement of scope.
Download Transfer Protocols certificationTransfer protocol paper
Source framework for the certified transfer-matching claims.
Open Transfer Protocols paperChatGPT access troubleshooting and support request checklist
| Problem | Recommended action |
|---|---|
| AI link does not load | Sign in to ChatGPT, then reopen the COMPASS AI link. |
| Custom GPT unavailable | Confirm that the account plan or workspace supports custom GPTs and file uploads. |
| Upload fails | Try a smaller PDF, CSV, or XLSX; remove scanned image-only pages; or test with a text excerpt. |
| Output is too general | Upload the static-app export and require citations to specific matrix, graph, or table entries. |
| Sensitive data concern | Stop, de-identify the data, or use a synthetic example. |
| BSU access issue | Use the BSU access dashboard and include the COMPASS component you need. |
Reusable documentation templates
Concept-analysis report
Course: code, title, reviewer, date, version.
Findings: gateways, bottlenecks, density, sequencing.
Evidence: matrix, analytics, graph, notes.
Next Steps: scaffolding, diagnostics, sequence, review.
Program-review note
Program: degree, concentration, catalog year, reviewer.
Findings: entry, hubs, chains, destinations.
Evidence: graph, edge list, state file, outcomes.
Next Steps: advising, prerequisites, metadata, assessment.
Transfer-review note
Incoming course: institution, number, title, credits, date.
Findings: exact, near, unmapped, missing, extra.
Evidence: map, syllabus, mapping, scores, diagnostics.
Recommendation: strong, conditional, partial, none, review.
Lean certification: what is checked and what remains human
Program Analyzer formal map and independent audit
Certified core
- Typed program graphs, reachability, SCCs, sequencing, and longest paths.
- Risk-component algebra, uncertainty, trend, and what-if identities.
- Conditional bounds for bounded inputs and admissible weights.
- An abstract contraction theorem for recursive propagation.
Independent verification
- Lean 4.28.0 and Mathlib v4.28.0.
lake buildcompleted 8,037 jobs across all 11 modules.- All 128 theorem declarations were replayed for axiom dependencies.
- Four non-fatal linter warnings occurred in
Examples.lean.
Scope boundary
- The integrated endpoint consumes precomputed risk components.
- Range results require explicit boundedness and weight hypotheses.
- Recursive propagation is abstractly certified under \\(\\lVert A\\rVert<1\\).
- Raw-data validity, causality, statistical coverage, and threshold policy remain external.
| Formal layer | Machine-checked content | Qualification |
|---|---|---|
| Typed foundation | Edge records, typed projections, observations, risk direction, clipping, and convex-combination lemmas. | Range conclusions require each theorem’s bounded-input and weight hypotheses. |
| Validation | Exact characterizations for missing endpoints, duplicate nodes/edges, and self-loops, plus additional predicates. | Not every advertised validation indicator has an if-and-only-if theorem. |
| Graph structure | Reachability, SCC/acyclicity, weak connectedness, corequisite contraction, and feasible block ranking. | The rank theorem produces natural-number levels, not an explicit topological list. |
| Structural metrics | Degree bounds, ancestor/descendant counts, longest paths, normalized depth, and classifications. | Normalized depth uses clipping where specified. |
| Risk algebra | Pooled rates, base risk, impact, exposures, bottleneck, pressure, fragility, combined scores, and sensitivities. | The [0,1] bounds require bounded components and nonnegative weights summing to one. |
| Recursive propagation | Existence and uniqueness for \\(x\\mapsto c+Ax\\) when \\(\\lVert A\\rVert<1\\). | No analyzer-specific \\(A=\\rho W\\) is instantiated, and no fixed-point [0,1] bound is proved. |
| Uncertainty and trends | Selected domain facts, shrinkage identities, interval-overlap symmetry, trends, and what-if sensitivities. | No certification of statistical coverage, Monte Carlo simulation, or every degenerate-input convention. |
| Determinism | The endpoint is deterministic for equal precomputed RunInput values. | runAnalyzer is not a raw-data-to-all-outputs composed theorem. |
Audit identity: July 10, 2026; source SHA-256 2186E5AF9C6F7FC94A56F3CAFB06228558403F0795F01F6D0DC1CBCD3E17CEFF; public ZIP SHA-256 9AB3CDCF79D8C6B007F667F278CEA3609BC90DCE37E257FF71A77E848CC43076. All 29 endpoints in the archive’s Part XIV list exist; the manuscript was absent, so completeness against its external requirement list was not independently tested.
Transfer Protocols certification
Confirmed
- Consistent comparison of incoming concepts with local profiles.
- Both methods return every strongest match, including ties.
- Consistent relabeling leaves results unchanged.
- Adding concepts cannot lower an individual course’s score.
- A clear leader survives changes too small to erase its lead.
How checked
- Aristotle completed all 24 submitted statements.
- The complete result was checked again independently.
- All five source files passed.
- Every original statement was preserved.
- The package includes the review record and evidence.
Limits
- At least one local course is required for a match.
- A runner-up comparison requires at least two courses.
- Faculty confirm syllabus and profile accuracy.
- Equivalence, fairness, policy, and final credit remain human responsibilities.
| Review area | Confirmed | Outside the certificate |
|---|---|---|
| Information setup | An agreed concept list and local-course profiles are used consistently. | Faculty confirm educational accuracy and meaning. |
| Course comparison | The two published comparison methods are applied consistently. | Departments select appropriate methods and settings. |
| Strongest matches | Every course tied for the strongest match is returned. | A strongest match is evidence, not an automatic decision. |
| Consistent labels | Consistent renaming does not change the result. | Splitting, combining, or redefining concepts requires review. |
| Additional concepts | Adding concepts cannot lower an individual course’s score. | Additional information may still change the first-ranked course. |
| Small changes | A clear leader remains first when edits cannot erase its lead. | Ties, inaccurate profiles, and major concept-list changes are excluded. |
| Repeatability | The repeatable version returns the protocol’s strongest-match set. | The live app and local review process were not certified. |
Certification summary: checked July 10, 2026; 24 statements confirmed; five source files checked successfully; Aristotle’s result was independently rechecked.
Concept Analyzer formal companion
Representation and graphs
- The value alphabet \\(\\{0,1,\\tfrac12,?\\}\\) and schema.
- Strict, co-dependency, and uncertainty graph construction.
- The transpose convention \\(m_{ij}=1\\Rightarrow C_j\\to C_i\\).
- Topological order, cycles, SCCs, and block sequencing.
- Reachability, uncertainty intervals, transitive reduction, and export auditability.
Analytic layer
- Bounded normalized betweenness centrality.
- A unique PageRank probability fixed point for \\(0<\\alpha<1\\).
- A deterministic bottleneck score once coefficients are fixed.
- Formal degree, reachability, acyclicity, and betweenness examples.
What remains human
- Graph theory cannot prove a prerequisite judgment is pedagogically true.
- Domain experts validate the submitted matrix.
- Decimal PageRank and application-specific bottleneck values are reproducible numerical evaluations.
| Layer | Certified content | Viewer-facing meaning |
|---|---|---|
| Representation | Unique strict, co-dependency, and uncertainty graphs. | The matrix has a precise graph meaning. |
| Transpose | Strict adjacency is the transpose of the strict-entry indicator. | A row concept requiring a column concept creates an edge from column to row. |
| Sequencing | Feasible strict orders exist exactly when the strict graph is acyclic. | All prerequisite arrows point forward in a valid order. |
| Cycles | A directed cycle rules out a strict linear order satisfying all stated dependencies. | A cycle is diagnostic evidence, not a software error. |
| Blocks | Co-dependency components can be sequenced as blocks when the block graph is acyclic. | Joint concepts are distinguished from strict prerequisites. |
| Reachability | Reach-in and reach-out count ancestors and supported descendants. | Gateway claims follow from graph paths. |
| Uncertainty | Lower and upper strict graphs bound completions of unresolved cells. | Unknown cells are not silently treated as facts. |
| Centrality | Betweenness, PageRank, removal effect, and bottleneck formulas are well-defined. | Scores are reproducible diagnostics, not curricular truths. |
| Export audit | A faithful export reconstructs the matrix and permits recomputation. | Reports can be checked outside the app. |
The archive reports a clean lake build and no sorry, admit, added axiom, or unsafe workaround. Certified endpoints depend only on standard Lean/Mathlib principles: propext, Classical.choice, and Quot.sound.
Suggested citations and public acknowledgements
Program Analyzer: Oussa, V. Lean 4 formal companion for the Program Dependency and Risk Analyzer’s deterministic graph-theoretic and algebraic core, 2026. Independently audited July 10, 2026.
Concept Analyzer: Oussa, V. Lean 4 certification archive for concept dependency matrices and curricular analytics, formal companion archive, 2026.
Transfer Protocols: Oussa, V., and Shama, U. COMPASS Transfer Protocols Certification: independent assurance for the published transfer-matching rules, 2026. Independently checked July 10, 2026.
Dr. Vignon Oussa
COMPASS development, maintenance, public curriculum-analytics ecosystem, and documentation framework.
Dr. Uma Shama
Strategic alignment, communication framing, and coauthorship of the Transfer Protocols framework.
Chigo Adigwe
Workflow requirements and usability feedback.
Lalitha Bhavanand
Implementation feedback and documentation refinement.
Nicole Medeiros
COMPASS documentation and project deliverables.
Accessibility and usability checks for editors
- Use descriptive link text and keep visible URLs for critical external resources.
- Do not rely on color alone; labels, headings, and table cells carry the interpretation.
- Keep diagrams simple, readable, and free of clipped labels.
- Add alt text or figure descriptions when adding screenshots or figures.
- Maintain a clear heading structure and PDF bookmarks after conversion.
- Prefer short paragraphs, meaningful headings, and scannable tables.
- Keep versioned source files and verify keyboard, mobile, reduced-motion, and print behavior before publication.