Research 

How to Use These Papers for Further Research & Experimentation:

The VerbaTerra papers are not meant to be read, cited, and shelved.
They are designed to be used as modular research instruments—to design experiments, extend simulations, and test new hypotheses within controlled bounds.

This section explains how to do that correctly.

1. Understand the Role of Each Paper

Each paper in the VerbaTerra corpus plays a distinct functional role. Treating all papers as equivalent will lead to misuse.

• Framework papers (e.g., ICLHF, CALR)
  Use these to define what exists in the system and what kinds of causal interactions are allowed.
  These papers constrain assumptions. They are not experiment results.

• Engine and system papers (vSION, SSEES)
  Use these to understand how simulations are constructed, what parameters exist, and what kinds of experiments are possible.
  These papers define the experimental playground.

• Validation and robustness papers
  Use these to understand how claims are tested, what counts as failure, and what must be replicated before extension.
  These papers define trust boundaries.

• Dataset and output reports
  Use these to ground any further analysis.
  All future work must remain constrained to the documented datasets unless explicitly stated otherwise.

2. Recommended Entry Paths for New Researchers

Depending on your goal, follow one of the paths below.

If you want to extend the theory

Start with:

• ICLHF (definitions, entities, causal ontology)

• CALR (resilience and adaptation logic)

Then:

• Identify an explicitly unmodeled variable or interaction

• Propose how it would integrate without violating existing constraints

• Design a simulation extension, not a narrative argument

If you want to design new experiments

Start with:

• vSION engine documentation

• SSEES experiment design notes

Then:

• Choose a single perturbation type (e.g., informational shock, technological spike)

• Define measurable outcomes before running anything

• Reuse existing metrics (NLIS / CRM) wherever possible

New experiments should alter conditions, not redefine the system.

If you want to validate or challenge results

Start with:

• Robustness & directionality validation papers

• Failure-boundary documentation

Then:

• Attempt replication using the same assumptions

• Apply controlled perturbations to test stability

• Explicitly document where results diverge or fail

Negative results are considered valid contributions if properly documented.

3. How to Form Research Questions (Correctly)

Good VerbaTerra research questions have three properties:

1. They are causal, not descriptive
   (e.g., “What causes epistemic drift under X?” not “How does drift look?”)

2. They are experimentally testable
   (i.e., they can be implemented as a simulation change or stressor)

3. They respect existing constraints
   (dataset limits, metric definitions, and validation protocols)

If a question cannot be turned into an experiment, it does not belong in this research program.

4. How to Run Follow-Up Experiments

All follow-up experimentation should follow this sequence:

1. State the hypothesis and expected direction of effect

2. Identify which framework assumptions are involved

3. Specify the perturbation or parameter change

4. Define evaluation metrics before execution

5. Run the experiment using documented configurations

6. Apply robustness and directionality checks

7. Document both successes and failures

Skipping steps weakens the validity of the outcome.

5. How to Report Extensions or Findings

Any extension, replication, or challenge should include:

• A clear reference to the originating paper

• Explicit statements of what was changed and what was held constant

• Metric-level results, not only qualitative interpretation

• A discussion of failure cases and edge conditions

All contributions should aim to be auditable, even if they are exploratory.

6. Scope, Limits, and Responsible Use

All VerbaTerra research outputs are simulation-grounded.

They should be used to:

• explore system behavior

• test causal hypotheses

• compare adaptive strategies

They should not be used as direct prescriptions for real-world policy or prediction without additional empirical validation.

Understanding the limits of the model is part of using it correctly.

7. Where to Go Next

• To reproduce results → start with validation papers

• To extend frameworks → begin with ICLHF / CALR specs

• To design experiments → follow vSION / SSEES documentation

• To collaborate or audit → consult the research repository and audit guidelines

This research program advances through careful extension, not uncontrolled expansion.

VerbaTerra welcomes external experimentation, replication, validation, and theoretical extension.
However, contributions must follow strict methodological and documentation standards to preserve scientific integrity.

This guide explains how to contribute correctly.

1. Types of Contributions We Accept

We recognize the following contribution categories:

Experimental Contributions

• New experiments built on existing frameworks (ICLHF, CALR)

• Extensions of vSION / SSEES simulations

• Controlled perturbation or stress-test studies

• Comparative experiments across existing simulation outputs

Validation Contributions

• Replication of published experiments

• Robustness and directionality checks

• Reverse-causality stress tests

• Failure-boundary exploration

Theoretical Contributions

• Formal extensions to existing frameworks

• Clarifications of assumptions or constraints

• Metric refinements or evaluation logic improvements

Documentation & Audit Contributions

• Reproducibility notes

• Audit checklists

• Experimental trace logs

• Clarification of ambiguous sections

2. What We Do Not Accept

To avoid scope creep and degradation of rigor, we do not accept:

• Narrative-only speculation without experimental grounding

• New datasets that bypass documented constraints

• Experiments that redefine core assumptions without justification

• Claims presented without validation or failure analysis

• Contributions that merge real-world data with simulations without disclosure

This is a research lab, not a sandbox.

3. How to Design an Experiment (Required Standard)

All experiments must be documented before execution.

Each experiment proposal must clearly specify:

1. Research question (causal, not descriptive)

2. Framework context (ICLHF / CALR assumptions involved)

3. Perturbation or modification introduced

4. Metrics used for evaluation

5. Expected direction of effect

6. Failure conditions (what would falsify the hypothesis)

If an experiment cannot be described this way, it is not ready to run.

4. Experimental Execution Rules

When running experiments:

• Use only documented configurations unless explicitly extending them

• Reuse existing metrics wherever possible (NLIS / CRM)

• Log parameter values and random seeds

• Preserve baseline runs for comparison

• Avoid post-hoc metric selection

All results—positive or negative—must be recorded.

5. Validation & Robustness Expectations

Every contribution that claims a result must include at least one validation step, such as:

• Perturbation stability testing

• Directionality checks

• Reverse-causality stress tests

• Cross-run consistency checks

Results that collapse under minimal perturbation are considered non-robust and must be reported as such.

6. How to Submit a Contribution

All contributions should be submitted through the research repository as one of the following:

• Pull request (preferred)

• Linked experiment report

• Structured audit note

Each submission must include:

• A short summary of the contribution

• References to relevant VerbaTerra papers or sections

• Clear documentation of what was changed or tested

• Links to logs, outputs, or reports

Incomplete submissions will be returned for revision.

7. Attribution & Credit

Contributors will be credited in:

• Repository acknowledgments

• Experiment logs

• Relevant publications (where applicable)

Authorship on formal papers depends on substantive intellectual contribution, not volume of activity.

8. Review Process

All contributions undergo:

• Initial scope and methodology review

• Validation and reproducibility check

• Documentation completeness review

Feedback may include:

• Requests for clarification

• Requests for additional validation

• Rejection with explanation

Rejection is not a failure—it is part of maintaining research quality.

9. Getting Started

To contribute effectively:

1. Read the Research Philosophy

2. Review the How to Use These Papers section

3. Choose a single, well-scoped contribution

4. Document before you run

5. Submit with transparency

Careful extension is valued more than rapid expansion.

10. Questions & Coordination

For questions about experiments, validation, or contribution scope:

📧 gupta.harshit98@gmail.com

We welcome contributors who respect constraints, document rigorously, and value reproducibility over speed.

This guide is intended for independent auditors, reviewers, and validation contributors who wish to examine VerbaTerra research outputs for methodological soundness, reproducibility, and integrity.

Auditing is not adversarial in this project—it is a core research function.

1. Purpose of Auditing in VerbaTerra

Auditing within VerbaTerra serves to:

• Verify experimental reproducibility

• Validate causal directionality claims

• Identify robustness limits and failure boundaries

• Ensure documentation completeness and traceability

• Surface hidden assumptions or methodological drift

Auditors are expected to challenge results, not endorse them by default.

2. What Can Be Audited

Auditors may examine:

• Framework definitions (ICLHF, CALR)

• Simulation architecture and configuration logic

• Experimental design and perturbation setup

• Metric definitions and evaluation logic (NLIS / CRM)

• Validation procedures and robustness checks

• Dataset manifests and experiment logs

• Published results and claimed interpretations

Audits may target individual experiments or the research program as a whole.

3. Auditor Entry Points

Recommended starting points for auditors:

1. Research Philosophy – understand scope, constraints, and intent

2. Validation & Robustness Documentation – understand how claims are tested

3. Dataset Manifest – verify dataset constraints and provenance

4. Specific Paper or Experiment – select a single, bounded audit target

Auditors are encouraged to start narrow and expand scope only after initial findings.

4. Auditor Checklist (Minimum)

A complete audit should address the following:

• Are all assumptions explicitly stated?

• Are causal claims directionally validated?

• Can the experiment be reproduced with provided documentation?

• Are metrics defined prior to execution?

• Do results persist under perturbation or stress?

• Are failure cases acknowledged and reported?

• Is there any mismatch between claims and observed behavior?

Auditors should document both confirmations and discrepancies.

5. Reproducibility Expectations

Auditors attempting reproduction should:

• Use documented configurations and parameters

• Preserve baseline runs for comparison

• Avoid undocumented modifications

• Log deviations explicitly if required

Failure to reproduce does not imply error by default; it must be contextualized.

6. Handling Discrepancies & Failures

If an audit identifies:

• non-reproducible results

• unstable outcomes

• undocumented assumptions

• metric inconsistencies

Auditors should:

• describe the issue precisely

• reference the relevant section or artifact

• document reproduction attempts

• avoid speculative interpretation

Well-documented negative audit findings are considered valid contributions.

7. Reporting Audit Findings

Audit reports should include:

• Scope of audit

• Artifacts reviewed

• Methods used

• Findings (positive and negative)

• Suggested clarifications or corrections

Reports may be submitted as:

• repository issues

• structured audit notes

• linked external audit documents

8. Auditor Independence & Ethics

Auditors are expected to:

• disclose conflicts of interest

• avoid selective reporting

• refrain from mischaracterizing intent or claims

• separate methodological critique from interpretation

Auditing is a technical process, not a reputational one.

9. Recognition & Credit

Auditors will be acknowledged in:

• audit logs

• validation records

• relevant publications (where applicable)

Auditing contributions are considered intellectual contributions, not ancillary work.

10. Coordination & Contact

For audit coordination, clarification, or access questions:

📧 gupta.harshit98@gmail.com

We welcome rigorous, transparent audits that strengthen the research and expose its limits.

VerbaTerra research outputs are released to encourage responsible reuse, extension, replication, and critique. This policy clarifies how the work may be used, cited, and built upon while preserving scientific integrity.

1. License & Access

Unless explicitly stated otherwise, VerbaTerra research artifacts—including papers, technical reports, frameworks, metrics, and documentation—are released under an open-source, permissive license.

This allows:

• academic citation

• non-commercial research reuse

• methodological extension

• independent replication and audit

Users are expected to comply with the terms of the applicable license specified in the repository or publication.

2. How to Cite VerbaTerra Work

All reuse must include clear and appropriate citation.

At minimum, citations should reference:

• the specific paper, report, or framework used

• the version or date of access

• the VerbaTerra Project as the originating research program

Example (generic format):

VerbaTerra Project. (Year). Title of Paper or Framework. Version / DOI / Repository Link.

Where available, please use the provided:

• DOI

• BibTeX entry

• CITATION.cff file in the research repository

3. Reuse of Frameworks & Concepts

Conceptual frameworks such as ICLHF, CALR, and related metric systems may be reused or adapted under the following conditions:

• The original framework must be explicitly acknowledged

• Any modifications or extensions must be clearly stated

• Reuse must not imply endorsement by the VerbaTerra Project unless explicitly granted

Framework reuse without attribution is considered improper academic practice.

4. Reuse of Simulation Logic & Experimental Design

Simulation architectures, experiment designs, and validation protocols may be reused for research purposes provided that:

• The original experimental assumptions are preserved or clearly documented if altered

• Results derived from modified systems are not presented as original VerbaTerra findings

• Any deviation from documented constraints (datasets, metrics, validation logic) is disclosed

Derived experiments should be labeled as extensions, replications, or variants, not originals.

5. Dataset Usage & Constraints

All datasets released by VerbaTerra are simulation-derived and subject to documented constraints.

Users must:

• cite the dataset source explicitly

• respect stated limitations and scope

• avoid presenting simulation outputs as direct real-world measurements

Reuse of datasets beyond their documented intent should be framed as exploratory.

6. Negative Results & Critical Reuse

VerbaTerra explicitly supports:

• publication of negative results

• replication failures

• critical analysis and alternative interpretations

Such work must:

• cite the originating artifact

• describe experimental differences precisely

• avoid mischaracterizing original claims

Critical reuse strengthens the research ecosystem and is encouraged.

7. What Is Not Permitted

The following uses are not permitted without prior written consent:

• Misrepresentation of VerbaTerra findings as empirical real-world evidence

• Commercial use implying endorsement or partnership

• Removal of attribution or origin references

• Selective citation that distorts the original conclusions

8. Attribution in Derivative Works

If you build upon VerbaTerra research, please include a brief attribution statement such as:

“This work builds upon the VerbaTerra research program, including the ICLHF and CALR frameworks and associated simulation methodologies.”

This helps maintain traceability across derivative research.

9. Collaboration, Permissions & Questions

For clarification, collaboration requests, or permissions beyond standard reuse, please contact:

VerbaTerra Research Team
📧 gupta.harshit98@gmail.com

We welcome responsible reuse that advances understanding while respecting methodological boundaries.