Research Protocol

Trifecta Protocol

From Concept to Complete Paper

Trifecta is a reproducibility-oriented research workflow that turns a conceptual seed into a simulation model, solved-variable structure, derivation and evidence chain, verified citation set, and LaTeX-ready scientific draft. It is designed to help researchers move from an idea to a testable research artifact without confusing internal protocol checks with external scientific proof.

◇
Deterministic SpecificationFrozen inputs, mappings, and validation rules.
≡
5-Module PipelineSimulation through publication synthesis.
✓
Validation DisciplinePrior art, counter-models, falsifiers, and audit artifacts.
Watch the Trifecta Protocol overview

How It Works

Five sequential modules move the research object from definition to a publication-ready draft while preserving assumptions, evidence boundaries, and failure conditions.

1
◇

SimuLock

Model the concept

Defines primitives, assumptions, variables, constraints, observables, and the simulation or conceptual model before downstream solving begins.

2
⚙

SolveMatrix

Resolve the unknowns

Maps known and unknown variables, equations, constraints, units, solvability conditions, and remaining unresolved terms.

3
▤

ProofChain

Pressure-test the derivation

Builds the claim and derivation chain, checks alternatives and counterexamples, and distinguishes internal consistency from empirical confirmation.

4
⌕

CiteWeaver

Check prior art

Searches relevant literature, verifies source identity and relevance, records what each source supports, and assembles usable citations.

5
▧

MetaDraft

Assemble the paper

Integrates the validated artifacts into a coherent manuscript with methods, results or predictions, limitations, falsification criteria, and references.

◎

Key Features

  • Frozen research inputs and dependency chain
  • Simulation and unknown-variable modeling
  • Derivation, counter-model, and falsification review
  • Prior-art and citation verification
  • LaTeX-ready manuscript synthesis
  • Six validation gates plus unresolved-issue reporting
☷

What You Need

  • A clear research or invention title
  • A primary objective or research question
  • A domain or field
  • A substantive concept description
  • Known constraints, if any
  • Access to Luminarch Prime
✧

Best For

  • New research hypotheses
  • Scientific and mathematical modeling
  • Technical problem solving
  • Experimental or computational concepts
  • Invention and methods development
  • Turning a mature concept into a paper draft
Protocol boundary: Trifecta can test structure, logic, reproducibility, literature support, and falsifiability. A simulation is not a physical result, an internally consistent derivation is not automatically a proof of nature, and an AI self-check is not independent empirical verification.
▧

Prompt Template

Copy the template, replace the bracketed fields, and paste it into Luminarch Prime.

Launch Trifecta Protocol.

Protocol:
Trifecta Protocol v4.2.1 — reproducibility-oriented research construction and scientific paper workflow.

Host:
Luminarch Prime.

RESEARCH SPECIFICATION

Research / Invention Title:
[INSERT TITLE]

Primary Objective or Research Question:
[INSERT PRIMARY OBJECTIVE]

Domain:
[PHYSICS / ENGINEERING / INFORMATION / BIOLOGY / SYSTEMS / CHEMISTRY / MATERIALS / OTHER]

Concept Description:
[PROVIDE A SUBSTANTIVE DESCRIPTION OF THE CONCEPT, PROPOSED MECHANISM, OR RESEARCH PROBLEM]

Known Constraints:
[LIST CONSTRAINTS, REQUIREMENTS, BOUNDARY CONDITIONS, OR NONE]

Inspiration Note, if useful:
[OPTIONAL CONTEXT OR NONE]

OPERATING RULES

1. Freeze the supplied research specification before the five-module pipeline begins. If a materially necessary input is missing, ask only the minimum clarification needed before proceeding.
2. Separate conventionally established evidence, user-supplied facts, UIPO-grounded definitions, UIPO/THD hypotheses, model assumptions, derived results, simulation outputs, and speculative extensions.
3. Do not treat simulation agreement, internal consistency, protocol reproducibility, or same-model review as independent empirical confirmation.
4. Do not invent citations, DOIs, datasets, measured values, experimental results, or prior validation. If a source cannot be verified, label it unverified rather than fabricating support.
5. Any mathematical or physical derivation must declare variables, types, units, domains, boundary conditions, assumptions, and unresolved quantities where applicable.
6. Any strong empirical claim must include an observable, comparator or null, uncertainty, falsification condition, and at least one credible alternative explanation.
7. When UIPO or THD is used, identify the exact dependency and distinguish a definition or mathematical proposal from an empirical hypothesis.
8. Preserve failed branches, null results, unresolved quantities, counterexamples, and validation warnings in the final record.

EXECUTE THE FIVE-MODULE PIPELINE IN THIS ORDER

1. SimuLock — MODEL THE CONCEPT
- Define the system boundary and research object.
- Identify primitives, assumptions, state variables, parameters, observables, and outputs.
- Specify equations or formal relationships where justified.
- State units, domains, boundary/initial conditions, and invariances where relevant.
- Define the simulation or conceptual model.
- Define abstention/failure states and what the model cannot determine.
- Produce a SimuLock artifact with a complete dependency map.

2. SolveMatrix — RESOLVE THE UNKNOWNS
- Separate known variables from unknown variables.
- Construct the governing equation, constraint, or dependency system.
- Check dimensional/type compatibility before solving.
- Determine whether the system is identified, underdetermined, overdetermined, singular, or conditionally solvable.
- Solve only what the available structure supports.
- Report alternative solutions and unresolved variables rather than forcing closure.
- Produce a SolveMatrix artifact showing each derivation step.

3. ProofChain — PRESSURE-TEST THE CLAIM AND DERIVATION
- State the central claim precisely.
- Build the dependency and reasoning chain from premises to conclusion.
- Type-check and dimension-check every critical equation.
- Separate mathematical implication, physical mechanism, statistical association, analogy, and causal claim.
- Search for the simplest counterexample, limiting case, and strongest conventional alternative.
- Identify circular reasoning, hidden assumptions, post-hoc choices, or places where the conclusion is built into the metric.
- Define what would falsify or materially weaken the claim.
- Do not label a claim proven unless the relevant proof obligations are actually satisfied.
- Produce a ProofChain artifact with claim ledger, counter-chain, and falsification record.

4. CiteWeaver — VERIFY PRIOR ART AND SOURCES
- Search the exact claim, closest conventional synonym, equivalent constructs in adjacent fields, known criticisms/counterexamples, and strongest competing framework.
- Prefer primary literature and authoritative sources.
- Verify source identity, DOI or stable bibliographic information where available.
- Record what each source supports and what it does not support.
- Separate prior art from novelty.
- Produce a clean reference set and citation map suitable for the manuscript.
- Never create a citation that cannot be verified.

5. MetaDraft — ASSEMBLE THE PAPER
- Integrate the frozen outputs from SimuLock, SolveMatrix, ProofChain, and CiteWeaver.
- Use the most appropriate scientific structure for the paper type rather than forcing IMRaD when it does not fit.
- Include: title, abstract, introduction, prior art, definitions/model, methods or derivation, results/predictions as applicable, discussion, limitations, falsification conditions, conclusion, and references.
- Distinguish actual results from proposed tests, simulations, or predictions.
- Preserve unresolved issues and evidence status in the manuscript.
- Produce LaTeX-ready content when requested.

VALIDATION GATES

Run and report the six Trifecta validation gates after the connected derivation is complete:

DIG — Deterministic Integrity Gate
Check input canonicalization, frozen dependencies, seed/version assumptions, and reproducibility conditions.

DLA — Discrete Lattice Anchoring
Check that all central terms, symbols, mappings, and relationships are anchored to explicit definitions.

CIG — Causal Isolation Gate
Check that the workflow does not convert simulation, correlation, analogy, or internal modeling into unsupported causal or physical claims.

AWARENESS_DRIFT — Synthesis Clarity and Drift Check
Check whether the analysis has drifted away from the original research objective, assumptions, or evidence boundary.

CFV — Controlled Field Validation
Check internal consistency across the five module outputs, equations, citations, assumptions, and conclusions.

ACCURACY — Scientific Accuracy Gate
Check physical plausibility, mathematical correctness, dimensional consistency, source validity, and claim calibration.

For every gate, report PASS / WARNING / FAIL and explain the evidence for that status. Do not self-certify a PASS merely because a checklist exists.

REQUIRED FINAL OUTPUT

A. Research Intake Record
B. Assumptions and Evidence Classification
C. SimuLock Artifact
D. SolveMatrix Artifact
E. ProofChain + Counter-Chain
F. CiteWeaver Prior-Art and Citation Map
G. Six-Gate Validation Summary
H. Falsification / Failure Table
I. Unresolved Issues and Required Next Work
J. MetaDraft Manuscript
K. Reproducibility / Audit Record

FINAL RULE
Build the model. Test the derivation. Challenge the claim. Verify the sources. Preserve what can fail. Then draft the paper.
↗

Ready to Create?

Copy the prompt template, add your research concept, and run the workflow in Luminarch Prime.

Open Luminarch Prime