Knowledge base
AuraScore 83/100

Quantitative Research Knowledge Base Modernisation Plan

Build an actionable plan to audit, standardise, and migrate mathematical and quantitative research documentation into an indexed knowledge base.

Use this template when transitioning complex analytical models, formula derivations, and mathematical proofs from legacy repos into an accessible knowledge base. It guides teams through standardisation, LaTeX validation, and structured article rollout.

Template

Role: Principal Mathematical Knowledge Architect with 12+ years of experience structuring computational research and quantitative documentation systems.

Context

  • Target Research Domain: {{research_domain}}
  • Current Repository State: {{legacy_repository_state}}
  • Mathematical Notation Standard: {{mathematical_notation_standards}}
  • Primary Knowledge Base Users: {{target_audience_skill}}
  • Deployment Platform: {{target_platform}}
  • Audit & Governance Cadence: {{governance_cycle}}

Task

Develop a comprehensive knowledge base modernisation plan that systematically audits, refactors, and publishes fragmented analytical documentation into a single-source-of-truth quantitative library.

Method

  1. Audit the {{legacy_repository_state}} to catalogue existing whitepapers, mathematical notebooks, and undocumented formula derivations across the {{research_domain}}.
  2. Define mathematical taxonomy classes separating theoretical proofs, computational algorithms, parameter matrices, and empirical validation logs.
  3. Establish baseline syntax and rendering rules enforcing {{mathematical_notation_standards}} across all text, code snippets, and embedded equations on {{target_platform}}.
  4. Design a tiered content architecture calibrated to the comprehension level of {{target_audience_skill}}.
  5. Formulate a 4-stage migration timeline covering ingestion, peer verification, formula rendering QA, and general release.
  6. Specify maintenance protocols adhering to the {{governance_cycle}} to prevent mathematical obsolescence as underlying models evolve.
  7. Detail continuous validation metrics focused on query precision, derivation bug reports, and knowledge reuse across teams.

Constraints

  • MUST enforce verifiable mathematical notation standards across all derived formulas.
  • MUST NOT leave equation variables undefined or without boundary condition notes.
  • Every stage of the rollout plan must define clear ownership and pass/fail gate criteria.
  • Milestones must be sequenced chronologically with clear resource assumptions.

Output format

Provide the strategic plan under four designated sections:

  1. Executive Summary & Taxonomy Schema (max 250 words)
  2. Phased Migration Schedule (table format with Phase, Milestones, Owner, and Exit Gate)
  3. Notation & Rendering Verification Standard Operating Procedure (numbered steps)
  4. Governance & Continuous QA Framework (max 300 words)

Self-review

  • Confirm all 6 context variables are explicitly referenced and integrated.
  • Ensure mathematical notation requirements are concrete rather than generic advice.
  • Verify the migration phases contain measurable entry and exit conditions.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-knowledge-base
complex-reasoning-analysis-math
knowledge-base
quantitative-research
documentation-plan