Proposed research framework

Follow change.
Preserve authority.

Connect qualified genetic context, longitudinal neurological observations, controlled research analytics, and independent assessment—without collapsing them into one claim.

Explore the framework

Platform narrative: INTRINSICA® Research · neurological specification v0.1

INVESTIGATOR-GOVERNED CORE GenotypingClinical + phenotypeIndependent endpointsFollow-up over time
01

What it is

A connected framework—not a treatment engine.

A therapeutic-agnostic proposal for bringing qualified genotype–phenotype evidence into study execution while keeping protocol authority, participant support, and independent endpoints distinct.

“A study captures outcomes. Connected research examines the story behind them.”

01

Context

Study genetic information alongside clinical and phenotypic data—not as an independent treatment instruction.

02

Continuity

Connect baseline characterization, repeated observations, treatment exposure, and follow-up.

03

Traceability

Link outputs to sources, qualifications, model versions, protocol purpose, and limitations.

04

Governance

Automate preparation and routing; preserve decisions for authorized investigators and study authorities.

Source basis · INTRINSICA platform narrative; neurological manual §§1–2

02

How it connects

Evidence moves through controlled boundaries.

Each layer has a defined role. Novel exploratory output takes a different route from established source values or protocol-defined safety thresholds.

INPUTS

Qualified sources

Genotyping reports, clinical assessments, participant reports, physiology, and protocol-specified laboratory or imaging data.

INTRINSICA

Controlled analysis

Qualification, pinned models, versioned outputs, uncertainty, and output classification.

ROUTING

Split by class

Permitted content may enter review. Novel Class X content routes to a sealed research store by default.

ECP

Study coordination

Review packets, decision records, authorized tasks, participant support, and exception queues.

ASSESSMENT

Independent reference

Protocol-defined endpoints recorded independently after predictions are timestamped.

Consent + disclosure scopeProtocol + configurationMasking + safetyAppend-only lineage

Source basis · neurological manual §§2, 7, 10, 13

03

Research journey

From study lock to bounded claims.

Select a phase to see what the workflow prepares, what must be accepted, and where authority remains.

Source basis · neurological S0–S10 workflow, condensed into six presentation phases

04

Neurological focus

Seven modules. Different questions. Shared discipline.

Every proposed module requires the core genotype panel and longitudinal phenotype. The measurements, independent references, and limitations change with the research question.

Source basis · neurological manual §5; workbook 04_Neuro_Modules

05

Study-design branches

The protocol changes what S7 may do.

“Investigator-initiated” describes leadership—not whether a study assigns an intervention. The study design determines the authorization branch.

Source basis · neurological manual §4; workbook 03_Study_Config and S7

06

Collaboration scope

What a research collaboration could include.

These are proposed workstreams and evidence products—not a representation that every capability is implemented or available for a named study.

01 · CONFIGURE

Study architecture

Translate an approved protocol into a versioned configuration with module selection, assessment schedule, role permissions, genotype requirements, APOE decision, output register, and independent references.

  • Protocol-to-workflow mapping
  • Study-specific readiness tracks
  • Masking-aware role design
  • Defined output permissions
02 · QUALIFY

Source readiness

Connect report identity, assay context, provenance, required calls, device metadata, visit windows, and phenotype completeness.

03 · ANALYZE

Research analytics

Run locked, prespecified comparisons with source links, version identifiers, qualification state, and explicit limits.

04 · COORDINATE

Investigator review + participant follow-up

Assemble permitted review packets, capture investigator decisions, coordinate protocol tasks, reminders, care-partner support where consented, and immediate possible-AE routing.

05 · EVALUATE

Separate evidence packages

Prepare distinct analyses for therapeutic effect, measurement validity, workflow utility, and the incremental contribution of genotype.

Source basis · INTRINSICA collaboration pathways; neurological manual §§7, 11, 14

07

Authority boundary

Automate preparation. Not authority.

Human review is necessary, but review alone does not transform an exploratory output into authorized decision support.

Software may

  • Qualify records against configured criteria.
  • Run pinned models on analysis-ready inputs.
  • Class outputs and preserve their lineage.
  • Assemble packets from release-eligible content.
  • Route tasks, reminders, questions, and possible safety signals.

Authorized people retain

  • Eligibility, clinical judgment, and treatment decisions.
  • Protocol, safety, and sponsor responsibilities.
  • Laboratory authorization and corrected reports.
  • Endpoint assessment and independent statistical interpretation.
  • Claim review, publication, and mode-switch approval.
Class X exploratory output → sealed store by default → no investigator or participant visibility → no clinical influence

Source basis · neurological manual §§2.1–2.3, 10–12

08

Evidence questions

One framework. Four questions that must not be merged.

Select an evidence question to see what it asks and the interpretive boundary it preserves.

Source basis · INTRINSICA “four separate questions”; neurological manual §14

09

Synthetic workflow simulator

Readiness is not one score.

Choose a synthetic state. Observe how separate tracks prevent an analytical issue from being mistaken for a care, support, or safety instruction.

Source basis · workbook synthetic validation scenarios; no patient, genotype, clinical, or outcome data

10

Research possibilities

Questions worth testing—not benefits presumed.

The framework is designed to make these questions prospectively testable and independently interpretable.

01

Does context add value?

Compare clinical-only, phenotype-enhanced, core-genotype-enhanced, and disease-extension models against an independent reference.

02

Who changes—and how?

Study repeated observations, trajectories, response heterogeneity, and recovery patterns without treating a model score as a clinical endpoint.

03

Does the workflow work?

Evaluate completeness, review, authorized execution, follow-up, exception handling, masking, and provenance as workflow questions.

04

Can an exploratory output progress?

Only through a prospective evidence package, resolved classification, locked version, defined context of use, permitted responses, and protocol/IRB authorization.

Source basis · INTRINSICA platform questions; neurological manual §§4.4, 14

11

Implementation readiness

Proposed architecture. Open activation dependencies.

At this version, the activation gate remains on hold. The dependencies below must be resolved for a named study; the presentation itself is not evidence that they are complete.

OPEN

Named host study

Protocol, statistical analysis plan, indication, sponsor responsibilities, and IRB approval.

OPEN

Qualified laboratory

Named laboratory, assay specification, applicable APOE method, variant reconciliation, and assay-specific acceptance criteria.

OPEN

Production validation

Computerized-system validation, role and masking tests, e-signature method, access controls, and production audit implementation.

OPEN

Output governance

Fixed classification register, resolved tier/class conflicts, novel-signal policy, and study-specific visibility permissions.

OPEN

Study operations

Confirmed instruments, versions, windows, systems of record, integration method, owners, and operational targets.

OPEN

Data + disclosure terms

Genomic authorization, disclosure policy, privacy controls, secondary-use rights, publication terms, and negative-result reporting.

Not represented

No implemented named study, validated neurological model, regulatory compliance determination, enrollment authorization, product release, or demonstrated clinical benefit.

Not claimed

No diagnosis, disease prediction, direct measurement of brain oxidative stress or neuroinflammation, autonomous prescribing, genotype-directed treatment, or automated device adjustment.

Source basis · neurological manual §§1, 15, 17

Research collaboration

Start with a neurological question that matters.

Discuss a sponsor-led trial, investigator-initiated study, prospective cohort, measurement collaboration, or independent evaluation pathway.

Visit INTRINSICA® Research ↗

Sources + interpretation

Primary public references

Controlled project basis

Interpretation boundary

The controlled neurological materials state that the workflow is proposed, not implemented for a named study, clinically validated, or established as regulatorily compliant. Workbook logic testing is not clinical validation. All simulator states in this presentation are synthetic administrative states; they contain no nucleotide calls, patient values, or outcome data.

Status boundary

Proposed implementation specification

What this presentation does

Explains the intended research architecture, role boundaries, module concepts, workflow branches, evidence questions, implementation dependencies, and synthetic logic states.

What it does not do

It does not claim an activated study, a qualified production system, validated neurological performance, regulatory compliance, clinical utility, therapeutic efficacy, diagnosis, disease prediction, or approved decision support.