SCFL / UCMS
Rules of Engagement & Institutional Research Program Q&A

Part I — Purpose and Governing Principles

1. What is being proposed?

The proposal is to establish an institutionally administered research program to evaluate, apply, and independently scrutinize SCFL/UCMS as an upstream structural measurement capability.

The program would begin with one bounded, technically defined measurement engagement using an existing dataset. It would not require a university to adopt the entire research corpus, endorse the underlying framework, or commit to a continuing program before evaluating the initial results.

The longer-term possibility is a coordinated research program in which multiple investigators examine distinct applications of upstream measurement under consistent governance, version control, and evidence standards.

The immediate objective is narrower: determine whether the measurement can be executed in a real research environment, produce interpretable outputs, and contribute useful information beyond an agreed conventional baseline.

2. What are the governing principles?

1. Measurement before prediction. Structural characterization, observed change, and predictive performance are distinct claims requiring different evidence.
2. Bounded scope. Each engagement has a defined dataset, question, observation window, protocol, deliverables, and stopping point.
3. Independent scrutiny. Researchers are not required to agree with the founder’s interpretations. Findings may be negative, inconclusive, or inconsistent with expectations.
4. Intellectual-property protection. The underlying operators and proprietary implementation are not transferred merely because an institution hosts a study.
5. Evidence proportional to claims. Demonstrations establish that a procedure was executed and produced outputs. They do not, by themselves, establish validity, generalizability, or predictive utility.
6. Version integrity. Each study identifies the measurement specification and implementation version used. Changes are documented and evaluated separately.
7. Modular research. Individual operators, application domains, and research questions may be evaluated independently. A negative finding in one application does not automatically invalidate every other component.
8. Institutional administration. The host institution, rather than the founder acting alone, manages the agreed administrative workload, research coordination, and project records.
9. Publication integrity. Research findings must not be suppressed or misrepresented to protect commercial interests. Confidential implementation details and publication rights are addressed explicitly before work begins.
10. No predetermined conclusion. The purpose of the program is to produce evidence, not to manufacture endorsement.

Part II — What Exists Today?

3. What has been developed?

SCFL/UCMS is a founder-developed body of work intended to characterize relational structure and changes in that structure within complex systems.

The work includes:

• A defined upstream measurement framework and associated terminology.
• A frozen SCFL v1.0 specification.
• A deposited Standard Bundle v1.0.
• A defined canonical operator set, with the operator code held privately.
• Candidate measures, temporal characterizations, and relational or seam-oriented analyses.
• A substantial research corpus spanning multiple application domains.
• Computational and retrospective investigations using selected real-world records, public data, and synthetic or simulated systems.
• Proposed service and reporting formats through which measurement outputs could be delivered without transferring the underlying operators.

The founder’s current corpus comprises approximately 173 papers and research artifacts. This figure is a description of the assembled body of work, not a claim that 173 independent peer-reviewed studies have established the validity of SCFL.

The program should begin with a controlled inventory identifying which artifacts are foundational specifications, which report experiments, which contain retrospective analyses, and which present hypotheses or proposed extensions.

4. What is the distinction between UCMS and SCFL?

UCMS — Upstream Coherence Measurement Stratum describes the broader measurement orientation and research program.

SCFL — Standard Coherence Fidelity Layer is the associated measurement framework intended to characterize relational structure and its changes.

The framework is intended to complement, rather than replace, established domain-specific methods. It does not assume that conventional indicators are useless, nor that SCFL automatically supersedes existing engineering, operational, biological, or organizational measurements.

The proposed research question is whether an additional upstream measurement layer can characterize structural conditions that are not adequately represented by selected conventional indicators.

5. What has been tested?

The existing work includes investigations across several domains, including power-system simulations and historical grid events, financial and organizational cases, healthcare-related data, industrial systems, and other complex-system applications.

Illustrative work includes:

• Analysis of historical power-system and market trajectories.
• N-1 contingency analysis using the ACTIVSg2000 simulated power-grid case.
• Retrospective examination of selected events and their associated data.
• Investigations of candidate measures and temporal changes in relational structure.

These studies provide starting points for identifying testable questions and candidate datasets. However, the current body of work is uneven in coverage, methods, controls, and evidentiary strength. Retrospective findings and simulations must not be represented as equivalent to prospective, independently replicated validation.

The host institution should receive an evidence register identifying, for each proposed pilot claim, the relevant dataset, analysis, comparison method, result, limitations, and outstanding validation requirements.

6. What has not yet been established?

The program must not assume that the following have been established merely because the framework, operator set, and prior studies exist:

• Independent validation across all proposed application domains.
• Reliable discrimination between systems that later fail and appropriate control systems that do not.
• Incremental value over well-chosen conventional indicators.
• Robustness to missing data, measurement artifacts, alternative preprocessing, and reasonable perturbations.
• Generalizability across institutions, datasets, and operating conditions.
• Operational or economic benefit at a level sufficient to justify deployment.
• Validated prediction of failure, collapse, or other adverse outcomes.
• Universal portability of the measurement across different kinds of systems.

These are potential subjects of research, not assumed deliverables.

7. How is the operator set fixed for a study?

Before a study begins, the operator code to be used will be fixed and identified by a SHA-256 fingerprint deposited as a public integrity record, so that every reported result can be traced to a specific version.

Freezing a specification supports traceability, attribution, and version-controlled evaluation. A cryptographic integrity commitment does not, by itself, prove that the operators are mathematically correct, scientifically valid, reproducible in every implementation, or useful in operational practice. Those questions remain open to appropriately designed tests.

Part III — What Is a Bounded Research Program?

8. What is meant by a bounded program?

A bounded program is a finite research engagement with explicit entry conditions, a defined scope, a documented execution, specified outputs, and a decision point. It is not an unrestricted invitation to explore every aspect of SCFL.

The initial engagement should include:

• One host institution or designated laboratory.
• One authorized dataset.
• One primary research question.
• One defined measurement configuration.
• One agreed observation interval or experimental scenario.
• One pre-agreed comparison baseline, where applicable.
• One technical report and supporting output package.
• One closing review and decision on whether further work is warranted.

The duration and cost should be determined after the dataset, access requirements, and technical scope have been assessed.

9. What should the first study attempt to establish?

The first study should answer a modest but consequential question:

The study should separately examine:

• Data suitability and measurement coverage.
• Successful and traceable execution.
• Interpretability of the reported outputs.
• Comparison with conventional indicators or documented reference conditions.
• Sensitivity to material data limitations.
• Evidence gaps and the next validation requirements.

The study need not establish failure prediction to be worthwhile. It must, however, distinguish a technically successful run from evidence that the measurement is useful.

10. What are the required deliverables?

The minimum deliverable package should contain:

• A. Measurement report — A concise statement of the question, scope, inputs, configuration, outputs, findings, and limitations.
• B. Structural state and change profile — The agreed SCFL outputs, including temporal observations where supported by the dataset.
• C. Measurement coverage and evidence register — A record of included data, missingness, exclusions, data quality, and the evidence supporting each reported conclusion.
• D. Baseline comparison — An agreed comparison against existing indicators, reference conditions, or suitable controls, where feasible.
• E. Method and integrity record — The specification version, configuration identifier, execution date, input fingerprint where permitted, and relevant integrity checks.
• F. Decision brief — A clear assessment of what the study established, what it did not establish, and whether the next step should be replication, a more demanding validation study, a revised measurement question, or termination.

A graph, score, or dashboard alone would not satisfy the proposed standard for a research engagement.

11. What would constitute success?

Success must be defined before execution. At the first stage, success means:

• The dataset meets the agreed requirements.
• The measurement runs under the documented configuration.
• The resulting outputs are interpretable enough to evaluate.
• The report identifies limitations and does not overstate the evidence.
• The baseline comparison produces a defensible assessment of incremental information, or establishes why such a comparison cannot yet be made.
• The institution can make an informed decision about whether further research is justified.

A technically successful execution with no demonstrated incremental value can still be a successful experiment if it answers the agreed question honestly.

12. What would constitute failure or a stopping condition?

The program must allow the following outcomes:

• The dataset is unsuitable.
• The required variables or temporal resolution are unavailable.
• The measurement cannot be executed reliably.
• Outputs cannot be interpreted consistently.
• Results are unstable under reasonable tests.
• The outputs add no meaningful information beyond the chosen baseline.
• The evidence is insufficient to justify further work.
• The cost or administrative burden exceeds the likely value.

The host and founder should agree on conditions under which the study is paused, revised, or terminated. No institution should be required to continue a program merely because substantial prior work has already been invested in the framework.

Part IV — Rules of Engagement

13. Who owns the intellectual property?

The founder retains ownership of the pre-existing SCFL/UCMS framework and proprietary operators, subject to any applicable pre-existing rights or agreements. The host institution does not acquire ownership of those materials simply by hosting a study.

The agreement must separately address:

• Pre-existing intellectual property.
• Access to the measurement engine.
• Ownership of newly developed software or modifications.
• Ownership and permitted use of study outputs.
• Research data ownership and stewardship.
• Rights to publish findings.
• Licensing and future commercial use.

Ownership of new inventions, improvements, and jointly developed materials must be negotiated rather than presumed.

14. Must the founder disclose the operators?

No. The proposed program does not require unrestricted disclosure of the frozen operators or proprietary calculation procedures. Depending on the study, execution may take place through a controlled local installation, a restricted service, or another agreed execution arrangement.

The institution must receive enough information to understand the outputs, assess the study’s limitations, and evaluate the claims being tested. The founder must not assume that withholding every aspect of the method will be acceptable for every academic project. The appropriate boundary should be negotiated before the institution commits resources.

15. Can researchers independently evaluate the results?

Yes. Independent evaluation is a central purpose of the program. Researchers may examine the data, assess data quality, select suitable baselines, test the stated hypotheses, analyze authorized outputs, and report findings under the agreed research protocol.

The program should not require researchers to endorse the framework, adopt its terminology uncritically, or treat its candidate measures as established scientific laws. Where independent reproduction of the full calculation is necessary to evaluate a claim, the parties must decide whether that level of access is compatible with the intellectual-property boundary. If it is not, the study must narrow its claims or use an alternative validation design.

16. Can the university publish the findings?

Publication should be addressed in the agreement before the study begins. The default objective is to permit accurate reporting of findings, including negative or inconclusive findings, while protecting legitimate confidential information and pre-existing intellectual property.

The parties should specify:

• Authorship and attribution principles.
• Treatment of confidential implementation details.
• Review periods for confidential information and patentable inventions.
• Rules for release of datasets and derived outputs.
• Any limits imposed by data-provider agreements or research ethics.
• How disagreements over interpretation will be documented.

The founder should not have an unrestricted veto over unfavorable scientific findings. Equally, publication must not inadvertently disclose protected operators or data that the institution is not authorized to release.

17. What about data security and research ethics?

The institution and founder must agree on data access, storage, processing, retention, and deletion before execution. The preferred initial datasets are existing engineering or infrastructure records for which authorization is clear and human-subject protections are not implicated.

Research involving people, identifiable records, sensitive health information, or regulated data may require additional institutional review, approvals, consent, and technical safeguards. Neither party should assume that de-identification alone resolves every legal or ethical obligation.

18. Can the university change the operators during the study?

The initial study should use an identified, frozen specification and documented configuration. Any material change should be recorded as a new version or configuration. Results from different versions should not be combined as if they were generated by an unchanged method. A modified version may be studied, but it should have a separate record and an appropriate comparison against the frozen version. This rule is intended to preserve traceability and make the findings interpretable.

Part V — Host Institution Responsibilities

19. What is the host being asked to administer?

The proposed host would assume responsibility for the agreed research-program administration, rather than merely lending its name or providing occasional introductions.

The administrative mandate may include:

• Appointing a program coordinator.
• Recruiting and coordinating faculty and student participants.
• Screening proposed datasets for suitability and authorization.
• Maintaining project documentation and the program register.
• Managing research agreements, budgets, and reporting.
• Coordinating institutional review and compliance.
• Establishing publication and research-integrity procedures.
• Scheduling project reviews and documenting decisions.
• Evaluating proposals for subsequent bounded studies.

The exact mandate must be matched to the host’s existing capabilities and available resources.

20. What does the host not automatically receive?

Hosting does not automatically confer:

• Ownership of SCFL/UCMS.
• Unrestricted access to the operators.
• Authority to license the method to third parties.
• Ownership of all pre-existing or future research artifacts.
• An exclusive right to the framework.
• Authority to represent the founder’s views as institutional endorsement.
• A guarantee of commercial returns or successful research outcomes.

Any additional rights must be separately agreed.

21. What staffing is required?

The minimum viable arrangement may require:

• One institutional sponsor or faculty champion.
• One designated program coordinator.
• One technical lead for the selected study.
• Appropriate student or research-assistant support.
• Access to data-governance, research-administration, and intellectual-property expertise when required.

These may be existing personnel with allocated time rather than new full-time hires. The initial pilot should determine the actual administrative burden before a permanent program structure is proposed.

22. Who pays for the program?

The funding model must cover both research execution and administration. Potential arrangements include:

• A sponsored pilot funded by an external organization.
• A university-supported capstone or research project.
• A foundation or philanthropic grant, where the proposed activity is eligible.
• A funded collaboration with a relevant industry or infrastructure partner.
• A phased program in which the first engagement establishes the case for subsequent funding.

The host should identify its administrative costs, direct research costs, and required overhead before commitments are made. The founder should not be expected to personally administer or finance an open-ended research program. Any founder compensation, licensing fee, or commercial arrangement should be disclosed and handled through an agreed process.

Part VI — Governance and Continuation

23. Who makes research decisions?

A proposed governance arrangement would separate three responsibilities:

• Program administration: The host manages schedules, budgets, agreements, records, and institutional compliance.
• Scientific evaluation: The designated researchers determine whether the data, analysis, and evidence support the study’s conclusions.
• Intellectual-property stewardship: The founder manages the pre-existing SCFL/UCMS framework and authorizes access to protected implementation under the agreement.

Disagreements should be documented and resolved through a predefined process. Neither administrative authority nor intellectual-property ownership should be treated as automatic authority over the other’s responsibilities.

24. How does the program expand?

Expansion should be earned through evidence and institutional capacity. A proposed progression is:

• Stage 1 — Feasibility: Confirm dataset suitability, permissions, scope, and technical requirements.
• Stage 2 — Bounded measurement: Execute one identified measurement study and deliver the agreed outputs.
• Stage 3 — Independent assessment: Evaluate the results against pre-agreed criteria, including suitable comparisons and limitations.
• Stage 4 — Replication or extension: Repeat the study, test another dataset, or investigate a more demanding question if justified.
• Stage 5 — Administered research program: Consider multiple projects, additional investigators, and continuing funding only after the host and founder agree that the evidence and administrative model justify expansion.

Each stage has its own decision point. Continuation is not automatic.

25. What is the first institutional commitment being requested?

The initial request is not for the university to endorse SCFL, establish a permanent laboratory, or assume responsibility for the entire research corpus. It is to identify an appropriate administrative home and scientific contact, review the proposed research boundaries, and determine whether one bounded measurement pilot is feasible.

If the institution is interested, the next step is a written pilot specification covering the research question, dataset, protocol, deliverables, intellectual property, publication, costs, and stopping conditions.

Part VII — The Founder’s Position

26. Why is institutional administration necessary?

The SCFL/UCMS corpus has grown beyond what one person can reasonably administer as a continuing, multi-domain research program. The founder’s contribution is principally the development and stewardship of the framework, its measurement specifications, its protected implementation, and the research questions that motivate its evaluation.

A sustainable program requires an institution capable of coordinating investigators, managing agreements and records, overseeing research processes, and administering funding. This is a practical requirement for continuity, not a request for institutional endorsement.

27. What does the founder seek from the institution?

The founder seeks an appropriate host, independent scrutiny, a disciplined first application, and a viable administrative structure. The objective is to establish whether SCFL can become a useful and responsibly governed measurement capability through evidence-generating research.

The founder is not asking an institution to accept every proposition in the existing corpus. The proposed arrangement is intended to make it possible to evaluate individual claims and applications on their merits.

28. What would the institution gain?

Subject to successful execution and mutually acceptable terms, the institution could gain:

• An opportunity to evaluate a new measurement approach.
• A bounded project using existing data and infrastructure.
• A research question suitable for student or faculty investigation.
• Potential technical reports and publishable findings.
• A possible basis for further sponsored research.
• A role in determining whether a continuing program is justified.

No research result, commercial opportunity, or external endorsement is guaranteed.

Part VIII — Initial Decision

29. What decision should be made now?

The initial decision is whether the institution is willing to explore hosting one bounded SCFL/UCMS measurement pilot under an explicit intellectual-property and research-governance agreement.

If yes, the parties should appoint contacts and prepare a pilot specification.

If no, the institution should be free to decline without obligation.

If the dataset, method, or proposed claims cannot support a meaningful and fair evaluation, the pilot should be redesigned or not undertaken.

← Back to Request to Measure (RTM) Research Program