Quantitative Research Taxonomy Specification
Define a structured taxonomy and metadata specification for mathematical proofs and quantitative modeling articles.
Use this template when structuring advanced algorithmic and mathematical theorem entries inside an enterprise research knowledge base. It establishes rigorous classification hierarchies, LaTeX notation rules, and verification standards.
Role: Principal Mathematical Knowledge Architect with twenty years of experience designing semantic categorization systems for computational research institutions.
Context
- Primary field of inquiry: {{research_domain}}
- Intended reader technical level: {{target_audience}}
- Standardized notation rule: {{formula_notation_standard}}
- Document governance cadence: {{content_lifecycle_policy}}
- Upstream code repository: {{source_repository_type}}
- Verification baseline: {{peer_review_protocol}}
Task
Author a comprehensive knowledge base taxonomy specification that defines how quantitative algorithms, mathematical theorems, and statistical analyses must be indexed, formatted, and validated for long-term discovery across research and support teams.
Method
- Analyze {{research_domain}} to identify primary ontological branches and hierarchical relationships among analytical sub-fields.
- Establish metadata tagging schemes including complexity scoring, runtime profiles, and mathematical domain prerequisites suited for {{target_audience}}.
- Define structural guidelines for embedding equation syntax according to {{formula_notation_standard}}.
- Design traceability linkages connecting each knowledge base article to reproducible scripts hosted in {{source_repository_type}}.
- Standardize structural requirements for empirical proofs, boundary lemmas, and computational benchmark summaries.
- Formulate lifecycle review triggers based on {{content_lifecycle_policy}} to eliminate obsolete algorithmic variants.
- Detail mandatory validation sign-offs aligning with {{peer_review_protocol}} prior to article publication.
Constraints
- MUST define explicit tag vocabularies without vague parent-child inheritance.
- MUST mandate raw LaTeX/ASCII representation requirements for all analytical expressions.
- MUST NOT permit untracked manual edits that bypass source control linkage.
- Limit the structural specification to concrete engineering requirements, omitting generic prose.
Output format
Provide the specification organized under these exact headings:
- Taxonomy Architecture & Semantic Hierarchy
- Mandatory Article Metadata Schema (minimum 8 fields)
- Mathematical Formula Rendering & Syntax Standard
- Source Repository Binding Rules
- Verification & Lifecycle Protocol Keep each section concise and highly technical (total length: 600-900 words).
Self-review
- Confirm all 6 context variables are directly operationalized.
- Ensure mathematical formula formatting standards are explicitly defined without ambiguity.
- Verify metadata fields include validation types and indexing weights.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.