The James Scott Institute for Frontier Sciences

James Scott InstituteFor Frontier Sciences

Rigorous intelligence infrastructure for science at the boundary of the known.

The James Scott Institute for Frontier Sciences develops evidence-governed frameworks for high-uncertainty research, scientific adversarial assurance, experimental validation, and defensible R&D decisions. Powered by KRYOS v6, the Institute helps qualified teams transform approved research materials into structured evidence maps, falsifiable hypotheses, artifact controls, optimized experiments, replication packets, and executive-grade decision systems.

As a physical lab incubator, the Institute works with qualified exotic- and frontier-science laboratories through approved facility, equipment, safety, access, and governance pathways. Its work is research incubation, not academic instruction.

Request Pilot Review Explore KRYOS Frameworks Learn About James Scott

Approved inputs only
Human-governed
Evidence-state labeling
No autonomous binding decisions
Reproducibility first
Dual-use aware

Institutional architecture — governance, KRYOS, modules, outputs

JAMES SCOTT INSTITUTE FOR FRONTIER SCIENCES

SCIENTIFIC GOVERNANCE LAYER · KRYOS v6

Inputs

Framework modules

Outputs

Select any input, module, or output above to see its required inputs, process, evidence boundary, and review owner. Nothing here reflects live processing of client data.

Institutional mandate

An institute built for the hardest category of scientific decision

Most research systems assume established questions and stable data. Frontier programs may face incomplete evidence, contested instruments, poorly mapped confounders, and strategic pressure that exceeds scientific maturity.

The Institute exists to impose structure on that uncertainty. Its role is not to manufacture confidence. Its role is to determine what is known, what is inferred, what remains vulnerable, what experiment carries the greatest information value, and what decision can be defended at the current evidence level.

Physical lab incubator

Infrastructure for qualified teams, not a classroom

JSIFS provides an institutional environment where approved laboratories can align physical research activity with KRYOS v6 evidence, assurance, security, and decision workflows.

Physical pathway

Facility, equipment, safety, access, and handling requirements are qualified before incubation begins.

KRYOS-guided R&D

Evidence maps, confounder attacks, experiment plans, replication packets, and decision systems remain linked to accountable laboratory work.

No unsupported promise

Acceptance, capacity, equipment, funding, outcomes, and validation are never implied by this public site.

Input and output schema

What you provide, and what the framework returns

Each output has a minimum responsible input set. Selecting either side shows the connection.

Select an input to see the outputs it can responsibly support, or select an output to see its minimum input set.

What you provide

What the framework returns

Framework ecosystem

Eighteen modules across intake, analysis, modeling, validation, security, governance, and commercialization

Filter, compare up to three modules, and assemble a candidate stack. Nothing here analyses scientific evidence — it plans which modules would apply.

Search framework modules

18 of 18 modules shown

KX-01 · Intake
Scientific Evidence Intake Kernel
Normalise approved research materials into a provenance-tracked evidence register.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Approved documents (papers, reports, notebooks) · Source inventory with ownership and handling class · Instrument and acquisition metadata where data is supplied
Process
Register each source with provenance, owner, date, and handling class.
Primary output
Provenance-tracked evidence register with initial labels and gap list.
Review gate
PI confirms the claim set reflects the programme's actual position.
Ideal use
Programmes with years of accumulated material and no single evidence view.
Evidence dependency
Produces Document-Supported and Data-Supported labels only.
Document-SupportedData-Supported
Open full page
Related domains: exotic-energy-investigation, high-uncertainty-anomaly-programs
KX-02 · Analysis
Source-Grounded Research Ontology
Build a shared vocabulary and relationship map across a programme's evidence base.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Evidence register from KX-01 · Programme glossary if one exists
Process
Extract entities, quantities, conditions, and apparatus references.
Primary output
Research ontology with source-linked relationships and contested-term register.
Review gate
PI ratifies contested definitions before downstream use.
Ideal use
Multi-team programmes preparing for a formal review or due-diligence process.
Evidence dependency
Inherits labels from source claims; adds no evidence strength.
Document-SupportedData-Supported
Open full page
Related domains: field-effects-and-materials-research
KX-03 · Analysis
God Particle Hypothesis Compression Engine
Compress a sprawling claim space into a small set of ranked, falsifiable hypotheses.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Research ontology · Observed effect descriptions with conditions · Known confounders
Process
Enumerate candidate explanations including mundane instrumentation causes.
Primary output
Ranked hypothesis table with falsification conditions.
Review gate
PI approves the retained hypothesis set and its ranking rationale.
Ideal use
Pre-funding triage for anomaly-heavy programmes.
Evidence dependency
Outputs are Hypothesis-level by definition.
HypothesisSpeculative
Open full page
Related domains: exotic-energy-investigation, advanced-propulsion-concepts
KX-04 · Analysis
Theory-to-Experiment Converter
Translate hypotheses into concrete measurement designs with declared controls.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Ranked hypotheses · Instrumentation inventory · Facility constraints
Process
Define independent, dependent, and nuisance variables per hypothesis.
Primary output
Experiment blueprint per hypothesis.
Review gate
Measurement-science reviewer signs off on validity before execution.
Ideal use
Programmes moving from exploratory runs to defensible measurement.
Evidence dependency
Blueprints are plans; they carry no evidence weight until executed.
HypothesisPilot-Validation Required
Open full page
Related domains: quantum-sensing-and-measurement
KX-05 · Modeling
Quantum Simulation / Digital Twin Lab Model
Build a bounded model of the apparatus and its environment to plan discriminating tests.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Apparatus description · Environmental conditions · Measured baselines
Process
Declare model scope, boundaries, and excluded physics.
Primary output
Digital twin model card, sensitivity results, and discriminating parameter regions.
Review gate
Modelling owner and experimental counterpart jointly accept the model card.
Ideal use
Deciding which of several expensive experiments to run first.
Evidence dependency
All outputs are Model-Inferred until experimentally tested.
Model-Inferred
Open full page
Related domains: quantum-sensing-and-measurement, aerospace-systems-rd
KX-06 · Validation
Deep Forensics and Artifact Elimination System
Attack the measurement before attacking the theory.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Raw data · Calibration records · Apparatus and environment description · Analysis code or steps
Process
Enumerate the artifact attack surface across instrument, environment, procedure, and analysis.
Primary output
Artifact elimination report with residual-risk statement.
Review gate
Independent internal reviewer confirms the artifact inventory is complete.
Ideal use
Propulsion and exotic-energy anomalies with small effect sizes.
Evidence dependency
Required before Experimentally Supported can be assigned.
Experimentally SupportedContradictedQuarantined
Open full page
Related domains: advanced-propulsion-concepts, exotic-energy-investigation
KX-07 · Modeling
Bayesian Active Experiment Planner
Rank candidate experiments by expected information gain under real constraints.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Ranked hypotheses · Cost and time estimates · Facility availability
Process
Elicit and document priors with rationale.
Primary output
Next-best-experiment queue with information-gain rationale.
Review gate
Sponsor and PI approve the queue before resource commitment.
Ideal use
Constrained programmes with more ideas than beam time.
Evidence dependency
Model-Inferred planning output.
Model-InferredPilot-Validation Required
Open full page
Related domains: high-uncertainty-anomaly-programs
KX-08 · Validation
Helios Multi-Agent Scientific Council
Run a structured multi-perspective review that surfaces disagreement rather than averaging it.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Evidence register · Artifact elimination report · Claim under review
Process
Run each role pass independently against the same evidence.
Primary output
Council review with preserved dissent and routed open questions.
Review gate
Named human reviewers own the final position; the council output is advisory.
Ideal use
Pre-gate review of a high-consequence claim.
Evidence dependency
Advisory only; assigns no evidence label on its own.
HypothesisModel-Inferred
Open full page
Related domains: exotic-energy-investigation
KX-09 · Validation
Contradiction Entropy Monitor
Track contradictions across the evidence base as it grows.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Evidence register · New results as they arrive
Process
Detect logical and numerical conflicts between claims.
Primary output
Contradiction register with owners and resolution states.
Review gate
Lab Director reviews the open contradiction register at each cadence point.
Ideal use
Long-running programmes with staff turnover.
Evidence dependency
Can downgrade claims to Contradicted or Quarantined.
ContradictedQuarantined
Open full page
Related domains: high-uncertainty-anomaly-programs
KX-10 · Security
Red-Team Scientific Claim Attack Engine
Attempt to defeat a claim using every defensible line of attack before anyone external does.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Claim statement · Supporting evidence chain · Artifact elimination report
Process
Restate the claim in its strongest defensible form.
Primary output
Red-team verdict with surviving objections and required remediation.
Review gate
PI responds to each objection in writing before the verdict is finalised.
Ideal use
Any claim that would change a funding or public position.
Evidence dependency
Can block elevation to Experimentally Supported.
ContradictedExperimentally SupportedQuarantined
Open full page
Related domains: advanced-propulsion-concepts, exotic-energy-investigation
KX-11 · Analysis
Weak-Signal Detection Layer
Characterise low-amplitude signals without inflating them into findings.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Raw data · Noise characterisation · Pre-registered detection criteria
Process
Characterise the noise floor and its drift.
Primary output
Detection report with false-positive budget and negative results retained.
Review gate
Statistical reviewer confirms the analysis matches pre-registration.
Ideal use
Quantum sensing and low-thrust propulsion measurement.
Evidence dependency
Can support Data-Supported at most on its own.
Data-SupportedContradicted
Open full page
Related domains: quantum-sensing-and-measurement, advanced-propulsion-concepts
KX-12 · Validation
Cross-Lab Replication Packet Generator
Package a result so an independent team can attempt it without contacting the originators.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Executed protocol · Calibration procedure · Acceptance criteria · Raw and processed data
Process
Write the protocol to a standalone level of detail.
Primary output
Replication packet ready for controlled external release.
Review gate
Compliance Lead clears the packet for external transmission.
Ideal use
Converting an internal result into an externally defensible one.
Evidence dependency
The route from Experimentally Supported to Independently Replicated.
Experimentally SupportedIndependently Replicated
Open full page
Related domains: field-effects-and-materials-research
KX-13 · Governance
Dual-Use / Compliance Gate
Screen outputs for dual-use, export, and handling exposure before release.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Draft artifact · Handling classification · Jurisdiction and institutional policy references
Process
Classify the artifact against declared handling classes.
Primary output
Release determination record with redaction recommendations.
Review gate
Compliance Lead records a named determination before release.
Ideal use
Programmes with security-sensitive or export-exposed subject matter.
Evidence dependency
Independent of evidence state; applies to all artifacts.
QuarantinedPilot-Validation Required
Open full page
Related domains: aerospace-systems-rd
KX-14 · Commercialization
Data Asset Valuation Engine
Assess the strategic value of a programme's data assets independently of claim status.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Data inventory with provenance · Collection cost basis · Rights and ownership position
Process
Inventory datasets with provenance and completeness scores.
Primary output
Data asset valuation with drivers and uncertainty statement.
Review gate
Commercialization Lead and counsel review the rights position.
Ideal use
Pre-partnership or pre-investment diligence.
Evidence dependency
Strong Industry Inference at best.
Strong Scientific InferenceModel-Inferred
Open full page
Related domains: field-effects-and-materials-research
KX-15 · Commercialization
IP and Technology Transfer Engine
Map protectable positions and transfer pathways against actual evidence state.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Evidence state summary · Invention disclosures · Institutional IP policy
Process
Map candidate protectable positions to their evidence states.
Primary output
Technology transfer pathway map with evidence prerequisites.
Review gate
Technology transfer office and counsel review before any external step.
Ideal use
Programmes preparing a first external partnership conversation.
Evidence dependency
Gated by the evidence state of the underlying claim.
Pilot-Validation RequiredStrong Scientific Inference
Open full page
Related domains: aerospace-systems-rd
KX-16 · Governance
Executive Scientific Decision Layer
Convert the evidence state into an accountable decision package.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Evidence register state · Red-team verdict · Contradiction register · Resource position
Process
Summarise the current evidence state in plain language.
Primary output
Executive decision packet with options, conditions, and owners.
Review gate
Sponsor and Lab Director countersign the packet.
Ideal use
Quarterly programme governance and stage-gate reviews.
Evidence dependency
Reflects, never elevates, the underlying evidence state.
Pilot-Validation RequiredExperimentally Supported
Open full page
Related domains: high-uncertainty-anomaly-programs
KX-17 · Governance
21–30 Day Pilot Orchestrator
Run a bounded pilot with declared cadence, gates, and stop conditions.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Scoped problem statement · Approved material inventory · Named review participants
Process
Phase 1: evidence intake and ontology build.
Primary output
Completed pilot package with phase artifacts and a stated recommendation.
Review gate
A named client reviewer signs each phase gate before the next begins.
Ideal use
First engagement on a high-uncertainty problem.
Evidence dependency
Pilot-Validation Required until acceptance criteria are met.
Pilot-Validation Required
Open full page
Related domains: exotic-energy-investigation
KX-18 · Governance
90-Day Scale Roadmap Engine
Define what a programme does after a pilot, conditional on the evidence it produced.
Institute module developed within the KRYOS v6 framework ecosystem.
Required inputs
Pilot package · Resource envelope · Governance constraints
Process
Define the evidence precondition for each 30-day block.
Primary output
Conditional 90-day roadmap with stop branches.
Review gate
Sponsor approves each block's precondition before the block begins.
Ideal use
Programmes preparing a funding case after a successful pilot.
Evidence dependency
Conditional planning output only.
Pilot-Validation RequiredModel-Inferred
Open full page
Related domains: aerospace-systems-rd

Framework stack builder

Your working stack (0)

Add modules above to assemble a candidate sequence. This is a planning interface only: it has not analysed any scientific evidence, and only framework identifiers are stored in your browser.

Workflow prompts

Operational prompt templates with inputs, gates, and failure conditions

Prompt templates provide structured analytical workflows. They do not establish the truth of a scientific claim. Full prompt packs and implementation guidance are available through qualified pilot review.

Workflow prompt

Frontier Evidence Intake Prompt

Convert a scattered materials set into a provenance-tracked claim register with initial evidence labels.

ROLE: Evidence intake analyst operating under an evidence-governed protocol.

SOURCES: [INPUT DOCUMENTS]
DATA: [DATASET]
INSTRUMENTATION: [INSTRUMENTATION]
CONSTRAINTS: [CONSTRAINTS]

TASK
1. Register every source with owner, date, locator, and handling class.
2. Extract discrete claims. For each claim, record the exact supporting locator.
3. Separate observation from interpretation. Flag any sentence that mixes both.
4. Assign an initial evidence label from: Document-Supported, Data-Supported,
   Model-Inferred, Hypothesis, Speculative, Contradicted.
5. List missing metadata as explicit open items. Do not infer missing values.
6. Do not resolve conflicts between claims at this stage; record them.

OUTPUT FORMAT: [OUTPUT FORMAT]
Return a table of claims plus a separate gap list and a separate conflict list.
State clearly which claims cannot be labelled at all and why.

Placeholders: [INPUT DOCUMENTS] [DATASET] [INSTRUMENTATION] [CONSTRAINTS] [OUTPUT FORMAT]

Open full prompt

Workflow prompt

Exotic Propulsion Artifact Audit Prompt

Enumerate and rank every artifact class capable of reproducing a reported thrust or force signal.

ROLE: Measurement forensics analyst. Assume a mundane cause until eliminated.

REPORTED EFFECT: [CLAIM]
DATA: [DATASET]
CALIBRATION: [CALIBRATION RECORDS]
APPARATUS: [INSTRUMENTATION]
KNOWN CONFOUNDERS: [KNOWN CONFOUNDERS]

TASK
1. Enumerate the artifact attack surface across at least these classes:
   thermal drift, vibration and acoustic coupling, electromagnetic coupling,
   cable and tether force, software or firmware leakage, environmental coupling
   (pressure, humidity, airflow, ground motion), sensor saturation and
   non-linearity, and interpretation bias.
2. For each artifact, state the mechanism and whether it could reproduce the
   full reported magnitude, part of it, or none of it.
3. Rank artifacts by reproducing power.
4. Specify one eliminating control per artifact, including null runs.
5. Audit the analysis pipeline for leakage, selection effects, and rounding.
6. State residual risk after all proposed controls.

OUTPUT FORMAT: [OUTPUT FORMAT]
Do not assign any elevated evidence label. Report only artifact status and
residual risk.

Placeholders: [CLAIM] [DATASET] [CALIBRATION RECORDS] [INSTRUMENTATION] [KNOWN CONFOUNDERS] [OUTPUT FORMAT]

Open full prompt

Workflow prompt

Quantum Simulation Boundary Prompt

Declare the validity boundaries of a digital twin before its output is used for planning.

ROLE: Modelling owner producing a model card for an experimental apparatus.

APPARATUS: [INSTRUMENTATION]
MEASURED BASELINES: [DATASET]
CONSTRAINTS: [CONSTRAINTS]

TASK
1. State model scope in one paragraph, then list excluded physics explicitly.
2. List every parameter with its range and the source of that range.
   Mark parameters that are assumed rather than measured.
3. Report sensitivity of the primary output to each parameter.
4. Identify parameter regions where competing hypotheses produce observably
   different predictions.
5. State the validity boundary: conditions under which this model must not be used.
6. Label all numerical output Model-Inferred.

OUTPUT FORMAT: [OUTPUT FORMAT]
Never describe a modelled quantity in language reserved for measurement.

Placeholders: [INSTRUMENTATION] [DATASET] [CONSTRAINTS] [OUTPUT FORMAT]

Open full prompt

Workflow prompt

Helios Council Review Prompt

Run six independent role-conditioned reviews and preserve their disagreement.

ROLE: Council facilitator. Run each role pass independently before any synthesis.

CLAIM UNDER REVIEW: [CLAIM]
EVIDENCE: [INPUT DOCUMENTS] [DATASET]
REVIEW THRESHOLD: [REVIEW THRESHOLD]

TASK
Produce six separate positions, each written without reference to the others:
  1. Experimentalist — protocol, controls, execution risk
  2. Theorist — internal consistency, competing accounts
  3. Metrologist — calibration, traceability, measurement validity
  4. Statistician — pre-registration, multiplicity, power, effect size
  5. Adversary — strongest defensible attack on the claim
  6. Compliance reviewer — provenance, handling, dual-use exposure

Then:
7. List every point of disagreement with its evidentiary basis.
8. Produce a synthesis that preserves minority positions verbatim.
9. Route each unresolved question to a named human owner.

OUTPUT FORMAT: [OUTPUT FORMAT]
Do not present this review as peer review. It is advisory input to human reviewers.

Placeholders: [CLAIM] [INPUT DOCUMENTS] [DATASET] [REVIEW THRESHOLD] [OUTPUT FORMAT]

Open full prompt

View all eight prompt templates

Scientific domains

Six domains with their confounders stated up front

Each domain page states the typical question, the confounders that dominate it, what the framework can help determine, and what it cannot claim.

Exotic Energy Investigation
Is the reported energy balance closed across all input and loss terms?
Common confounders
Unaccounted input power paths · Instrument calibration drift and traceability gaps · Thermal mass and time-constant effects · Power-factor and waveform measurement error · Sampling and integration-window mismatch
Cannot claim
That an anomalous energy balance is real without replication-grade evidence
Open domain detail
Advanced Propulsion Concepts
Does the measured force survive a full artifact attack surface review?
Common confounders
Thermal drift · Vibration · Electromagnetic coupling · Cable force · Software leakage
Cannot claim
That a propulsive effect is real prior to independent replication
Open domain detail
Quantum Sensing and Measurement
Is the claimed sensitivity supported by an independent noise characterisation?
Common confounders
Noise floor drift over acquisition windows · Post-hoc detection thresholds · Multiple-comparison exposure · Cross-talk between channels · Reference and clock instability
Cannot claim
A detection that survives only under post-hoc analysis choices
Open domain detail
Field Effects and Materials Research
Is sample provenance complete enough to attribute the effect?
Common confounders
Batch-to-batch variation · Sample history and ageing · Surface contamination and oxidation · Handling and mounting variation · Measurement-induced modification
Cannot claim
A materials effect without batch-level controls
Open domain detail
Aerospace Systems R&D
Which subsystem claims rest on qualification evidence versus analysis?
Common confounders
Analysis substituted for qualification testing · Environment mismatch between test and operation · Interface assumptions undocumented across teams · Heritage claims from non-equivalent configurations · Margin accounting inconsistencies
Cannot claim
Flight qualification or airworthiness of any system
Open domain detail
High-Uncertainty Anomaly Programs
Which anomalies are worth spending the next funding cycle on?
Common confounders
Selection effects in what gets reported · Instrument changes between observation epochs · Loss of provenance across staff turnover · Confirmation pressure from sponsors or critics · Inconsistent terminology across teams
Cannot claim
That an unexplained observation indicates a novel phenomenon
Open domain detail

Workflow sequence

Ten stages, each with a gate and a pause condition

Switch annotation views to see the same workflow from a scientific or a security-engineering perspective. The underlying sequence does not change.

Annotation view

Stage 01 — Approved Input Intake

Participants: PI, Compliance Lead, intake analyst
Required inputs: Approved source inventory with handling classes
Activity: Register sources, owners, dates, and handling classification.
Produced artifact: Source register
Gate to advance: Compliance Lead confirms every source is cleared for the engagement.
Pause condition: Material appears outside the approved handling class.

ScientificAcquisition conditions and instrument identity are recorded before anything is read for meaning.

Participants: PI, Compliance Lead, intake analyst
Required inputs: Approved source inventory with handling classes
Activity: Register sources, owners, dates, and handling classification.
Produced artifact: Source register
Gate to advance: Compliance Lead confirms every source is cleared for the engagement.
Pause condition: Material appears outside the approved handling class.

ScientificAcquisition conditions and instrument identity are recorded before anything is read for meaning.

Anticipated output architecture

Eighteen report sections with evidence conditions and review owners

Filter by role or evidence state to see which sections a given reviewer receives and what blocks issuance.

Filter by role

Filter by evidence state

18 of 18 sections shown

What the client receives
A single-page statement of position with explicit limitations.
Purpose
State in plain language what is currently supported and by what evidence.
Format
One page, no figures
Typical user
Sponsor
Review owner
Lab Director
Decision supported
Whether to continue, pause, or escalate the programme.
Example output structure
What is supported · What is not supported · What would change the answer · Limitations
Conditions preventing issuance
Evidence register is stale; Open red-team objections unaddressed
Known limitations
Compresses nuance by design; always read with the scientific boundary section.
SponsorCTOLab Director

Governance and scientific boundary

Evidence labels define what a claim rests on

Labels are descriptive, never aggregated into a score. Each pairs a distinct shape with text so status is never conveyed by colour alone.

Evidence labels

Document-Supported

Meaning: A statement traceable to a supplied document, paper, patent, or notebook entry.
Minimum evidence: At least one identified source with locatable passage and provenance record.
Permitted use: Describing prior art, stated methods, and claimed conditions.
Prohibited interpretation: Treating a documented claim as a measured or reproduced result.
Required reviewer: Principal Investigator or delegated research analyst.
Upgrade path: Attach primary data and calibration records to reach Data-Supported.
Downgrade / quarantine trigger: Source withdrawn, unverifiable provenance, or contradicting primary record.

Operating rules

01Never convert uncertainty into false certainty.
02Never claim extraordinary breakthroughs without replication-grade evidence.
03Preserve accountable human review at every gate.
04Separate scientific proof from commercialization potential.
05Separate observed data from interpretation.
06Preserve null and contradictory results in the record.
07Maintain provenance and audit history for every claim.
08Keep dual-use analysis at governance-safe levels of detail.
09Quarantine unsupported or compromised claims rather than deleting them.
10State limitations in every executive output.

Decision outcomes

Where an evidence state can legitimately lead

Every branch states its minimum evidence condition, decision owner, required next artifact, and reversal condition.

Recommendations are subject to authorized human judgement. The map shows routes, not conclusions.

Decision branch

Proceed

Operational rationale: Evidence supports continued investigation at the current scope.
Minimum evidence condition: Data-Supported with an accepted residual-risk statement.
Primary decision owner: Lab Director
Required next artifact: Next-best-experiment queue
Reversal condition: A new artifact class is found capable of reproducing the effect.
Governance note: Proceeding is not endorsement of any interpretation of the effect.

Intellectual architecture

A traceable line from systems philosophy to institutional application

James Scott

First-party documented

Systems architect and institutional founder.

This relationship describes intellectual and institutional lineage; it is not scientific validation.

Open related page

Accessible lineage list

01 James Scott — Systems architect and institutional founder.
02 Systems philosophy — Capability, evidence, auditability, human sovereignty, and institutional continuity.
03 Strategic Capability Philanthropy — Durable capability transfer rather than temporary dependency.
04 Framework ecosystem — ARCS, ARCF, OmniSynth, Helios, V-Framework, and Leverage Pyramid.
05 KRYOS v6 — Evidence-governed integration and decision-support architecture.
06 James Scott Institute for Frontier Sciences — Institutional governance and physical lab-incubator environment.
07 Programs, pilots, publications, decisions — Governed applications with named review owners and explicit limits.

Founder and systems architect

James Scott

James Scott is a technologist, systems architect, institutional founder, and architect of Strategic Capability Philanthropy. He founded Embassy Row Project and created the KRYOS framework ecosystem, including ARCS, ARCF, OmniSynth, Helios, the V-Framework, and the Leverage Pyramid.

Through the James Scott Institute for Frontier Sciences, Scott applies this architecture to qualified exotic-science and frontier-science laboratories using evidence-governed research, experimental skepticism, security awareness, and accountable human judgment.

Read James Scott’s Biography Explore Framework Lineage

Pilot inquiry

Bring a high-uncertainty research problem into a governed pilot.

Initial contact is for qualification and scoping only. No research materials are transmitted at this stage; approved materials are requested through a controlled channel after qualification.

Organization (required)

Role (required)

Scientific domain (required)

Current bottleneck (required)

Available material types (optional)

Indicate categories only. Do not describe the content of any restricted material.

Desired timeline (required)

Work email (required)

Non-sensitive message (optional)

Do not submit classified, export-controlled, proprietary, patient-identifiable, or otherwise restricted technical material through this form. Initial submissions should contain non-sensitive scoping information only.

I confirm this submission contains non-sensitive scoping information only, and I understand that no confidentiality guarantee applies to a public web form.

Human verification (required)

Complete the challenge below. A fresh verification is required for each submission attempt.

Verification not yet completed.

James Scott InstituteFor Frontier Sciences

Scientific Evidence Intake Kernel

Source-Grounded Research Ontology

God Particle Hypothesis Compression Engine

Theory-to-Experiment Converter

Quantum Simulation / Digital Twin Lab Model

Deep Forensics and Artifact Elimination System

Bayesian Active Experiment Planner

Helios Multi-Agent Scientific Council

Contradiction Entropy Monitor

Red-Team Scientific Claim Attack Engine

Weak-Signal Detection Layer

Cross-Lab Replication Packet Generator

Dual-Use / Compliance Gate

Data Asset Valuation Engine

IP and Technology Transfer Engine

Executive Scientific Decision Layer

21–30 Day Pilot Orchestrator

90-Day Scale Roadmap Engine

Your working stack (0)

Exotic Energy Investigation

Advanced Propulsion Concepts

Quantum Sensing and Measurement

Field Effects and Materials Research

Aerospace Systems R&D

High-Uncertainty Anomaly Programs

01Approved Input Intake−

02Evidence Classification+

03Ontology Build+

04Hypothesis Compression+

05Simulation / Digital Twin+

06Artifact Attack-Surface Review+

07Experiment Optimization+

08Red-Team Challenge+

09Replication Packaging+

10Executive Decision Readout+

P1Evidence Intake and Research OntologyDays 1–7−

P2Hypothesis, Model, and Artifact EngineeringDays 8–14+

P3Experiment OptimizationDays 15–23+

P4Red Team, Replication, and DecisionDays 24–30+

Six non-sensitive questions

OA-01Executive Answer▣Document-Supported−

OA-02Scientific Boundary▣Document-Supported+

OA-03Input and Evidence Inventory▣Document-Supported+

OA-04Research Ontology▣Document-Supported+

OA-05Hypothesis Compression Table○Hypothesis+

OA-06Digital Twin / Modeling Plan◇Model-Inferred+

OA-07Artifact and False-Positive Controls◧Data-Supported+

OA-08Next-Best-Experiment Queue◇Model-Inferred+

OA-09Scenario Mesh◇Model-Inferred+

OA-10Red-Team Verdict◧Data-Supported+

OA-11Replication Packet◆Experimentally Supported+

OA-12Compliance and Dual-Use Gate▣Document-Supported+

OA-13Data Asset Valuation▷Strong Scientific Inference+

OA-14IP and Technology Transfer Pathways⧗Pilot-Validation Required+

OA-15Executive Decision Packet⧗Pilot-Validation Required+

OA-1621–30 Day Pilot Plan⧗Pilot-Validation Required+

OA-1790-Day Scale Roadmap⧗Pilot-Validation Required+

OA-18Final Verdict◆Experimentally Supported+

Document-Supported

Proceed

James Scott

Bring a high-uncertainty research problem into a governed pilot.