Deterministic scientific claim gate

CAPAS compiles supplied evidence into a claim admissibility decision.

Claim plus evidence goes in; ACCEPT, REWRITE, REJECT, or HOLD comes out. CAPAS does not certify scientific truth. It decides whether supplied evidence licenses a claim for controlled reuse in reports, datasets, or fine-tuning.

Talk to pilot owner See pilot package
10kstructured payload validations
34%rewritten or rejected before reuse
417hmodeled review capacity
Recent Gate DecisionsSCHEMA V3
ACCEPTstatistical_confidence: p=0.03 <= alpha=0.05schema v3
REWRITEdirection not independently licensedtraining 7/14
REJECTartifact unavailable for reproducibilityaudit trail
HOLDRO-Crate and reviewer attestation pending CLI verificationno LLM

CAPAS workflow

mode → evidence → gate
Mode selection is Step 1. Evidence construction is Step 2. Gate execution is Step 3.
Step 1 of 3 · Choose

Only one mode is active at a time. Pick how you want to create or provide the claim evidence.

Choose a claim type, write the claim, then complete only the evidence fields required by that type.

Choose a claim type to see what CAPAS checks.

The evidence contract on the right updates as you work. The payload is built internally before the gate runs.

Batch Evaluation input
Evaluate many claim/evidence records using the same deterministic rules. Paste a JSON array, an object with items or claims, or a single payload to auto-wrap as one item.
Extraction is not a decision
Candidate rows are proposals only. A reviewer must inspect evidence spans and click Confirm & build payload before Step 3 can run CAPAS.

Run the selected workflow through the deterministic CAPAS gate. Step 3 never changes mode.

Payload status Guided Claim Builder
Mode selected Evidence pending Schema pending Gate not run

Build or provide evidence in Step 2, then run the deterministic gate here.

Try an example payload
Examples:

CAPAS deterministic claim gate

Raw JSON (Advanced)
Waiting for input...
Raw JSON Payload is the advanced path. Paste or inspect schema v3 JSON here, then run the gate from Step 3.
Payload loaded
Decision
EXAMPLE — a sample claim-drift decision (association → causation wording). Clear it, or run your own claim, to replace this.
Awaiting decision. Run a claim and this becomes a deterministic admissibility certificate — not a black box. It will show:
  • the verdict (ACCEPT / REWRITE / REJECT / HOLD) and the rule that fired
  • the licensed reuse boundary — exactly what the evidence permits
  • blockers and open proof obligations
  • the next operational action and fine-tune readiness
  • the raw, re-derivable JSON + audit hash
Press Run CAPAS Gate in Step 3 — missing evidence will HOLD, by design.
Decision inspector will summarize the verdict, fine-tune readiness, schema errors, provenance, and raw JSON.
Full output JSON 

        

      

    

  








  

    
Audit trail

    

      
      
      
      
      0/50 saved
    

  

  

    
    
  

  

    
No decisions yet.