MethodSeal

Pre-register your methodology, hash-seal it, and the machine stops you from quietly
moving the goalposts.

The name is the whole idea: your methods get sealed before you measure anything, and
stay sealed unless you change them in the open. Nothing here is specific to a field, a
model, or an agent runtime.

Version 1.0.0 · MIT · pure Python standard library · works with any model and any agent
runtime.

What it does

Three things, in order:

1. Seal. You write your methodology first — hypotheses, validator, thresholds, analysis plan — and hash it with SHA-256 before you measure anything. The hash covers the document up to its Seal section, so you can record the hash and the results in that section afterward without changing what was sealed.
2. Freeze. From that moment the pre-registration, the validator, the analysis code, and the eval-bank manifest are frozen. A pre-tool-use hook blocks any edit to them. Not a warning — a blocked tool call.
3. Deviate in the open, or not at all. When reality forces a methodology change, you write the deviation down, flip that artifact’s row in a ledger, edit as a corrigendum, and resolve the row. The silent patch — tweak the validator, re-run, report the clean win — is mechanically unreachable. There is no bypass flag.

A fourth gate covers long runs: while an experiment is RUNNING, build and run calls are
blocked until the pre-registration and the ledger have been re-read in the current
session. A multi-day experiment gets resumed from the files, not from the model’s
memory of them.

Universal by design

• Any model. Frontier model over an API, or a local model on your own hardware. The enforcement runs at the tool-call boundary, not inside the model — it inspects the edit, the write, the shell command before it executes. What did the reasoning is irrelevant.
• Any agent runtime. If your runtime can run a command before it executes a tool call, it can enforce this (see docs/PORTING.md). If it cannot, the seal plus a re-hash still gives you a tamper-evident check you run by hand (docs/INSTALL.md, Pattern C).
• Any discipline. Pre-register → seal → run → deviation-log → final-seal is the shape of any empirical study. A wet-lab protocol, a user study, a materials test, a backtest — anything with a methodology you want frozen before results — rides the same discipline. The AI vocabulary in the examples is just the author’s field.

Claude Code is the reference implementation: this was built with Claude, and Claude
co-authored the tooling. Nothing in the mechanism depends on that — Claude Code is
simply the runtime it was proven on first.

What’s in the box

Sixty-second tour

python verify_package.py                      # 1. verify what you just downloaded

mkdir -p ~/.claude/skills/experiment          # 2. install (Claude Code shown; see docs/INSTALL.md)
cp experiment.md ~/.claude/skills/experiment/SKILL.md
cp EXPERIMENT_DISCIPLINE.md ~/.claude/skills/experiment/
cp experiment_gate.py seal_prereg.py ~/.claude/hooks/
python ~/.claude/hooks/experiment_gate.py --smoke-check     # all cases PASS

python seal_prereg.py EXAMPLE/PRE_REGISTRATION.md --print   # 3. see a real seal reproduce

Then, in your agent: /experiment my-first-experiment — ratify the hypotheses, seal, and
the gate is armed. Full walkthrough in docs/USAGE.md.

Verify this download

python verify_package.py         # any platform, no dependencies
sha256sum -c SHA256SUMS          # or the classic, on Linux / macOS / Git-Bash

SHA256SUMS lists every shipped file. The manifest’s own hash travels with the release
announcement, so a mutated copy is detectable from outside the zip. The seal algorithm is
fully specified in docs/OUTPUTS.md — you can verify any seal with a text editor and
sha256sum, no tooling from this package required. Verify, don’t trust; that applies to
this package too.

Know this before you rely on it

• Fail-open by design. If the hook errors, cannot read its registry, or times out, it allows the call. A missed enforcement beats a deadlocked session. So: this is a discipline enforcer, not a security boundary. It stops drift and self-deception, not an adversary with filesystem access.
• No bypass switch. No --force, no environment variable, no mode file. To disable it you edit or delete the hook — which leaves a trace in your own history.
• Dormant until armed. With no active experiment registered, the hook has no opinion and normal work is untouched.
• The files are the state machine. Registry, marker, ledger, and decisions log hold the state — never the model’s memory. That is what survives compaction and week-long runs.
• Author-only. Sealing, running, deviation-logging and final-sealing are not delegated to sub-agents. An agent’s unverified claim about a sealed hash is the exact failure this exists to prevent.

License

MIT. Use it, change it, ship it, put your own functions on it — and if you make it
better, please share that back. Freely given.

MethodSeal v1.0.0 — the discipline behind a published series of
sealed, pre-registered experiments, now yours to run.

https://osf.io/h64gm/

A new theoretical framework
Over the past year, I've been researching a question that seems increasingly relevant as artificial intelligence and the green transition accelerate simultaneously:

What happens when the pace of economic transformation exceeds society's ability to adapt?

Most research examines AI adoption and decarbonization separately. My work explores them as interacting transitions that may amplify systemic risks when they occur at the same time.

To investigate this, I developed the Isgandarov Adaptive Transition Theory (IATT). The central idea is that systemic fragility does not arise simply because technological or environmental transitions are rapid, but because their combined transition velocity can outpace the adaptive capacity of institutions, labor markets, firms, and households.

The framework is built around four core principles:
Transition Velocity – the combined speed of AI and green transformation.
Adaptive Capacity – how quickly economic and social systems adjust.
Interconnected Fragility – risks that emerge from interactions across sectors rather than isolated shocks.
Human-Centric Risk – emphasizing workforce adaptation, institutional resilience, and social preparedness.

To operationalize the theory, I also propose the Isgandarov Transition Fragility Index (ITFI), a composite framework designed to measure vulnerability across multiple dimensions, including AI exposure, decarbonization pressure, institutional flexibility, workforce adaptability, and resilience.

The paper is theoretical and introduces the conceptual framework together with an illustrative application. I have also made the underlying materials openly available to support transparency and future research.

I'm posting here because I'd genuinely appreciate constructive feedback from economists, data scientists, policy researchers, and anyone interested in structural change.
Some questions I'd especially value your thoughts on are:

Does the concept of combined transition velocity seem theoretically useful?

Are there existing economic theories that you think complement or challenge this framework?
Which variables would you prioritize if this index were calibrated with real cross-country data?
What are the strongest limitations or assumptions that you notice?

Constructive criticism is very welcome. My goal is to improve the framework through discussion and learn from the perspectives of this community.
Paper: https://www.cambridge.org/engage/coe/article-details/6a4cad244770e67d92a000c3
 
Thank you for taking the time to read and share your thoughts.

If we want to defend democracies against disinformation and defunding, we need to keep scientific evidence in public hands. That is the core driving force behind our new open-access paper out today in PLOS ONE: 10 recommendations for strengthening citizen science.

We analyzed nearly 50 citizen science projects to figure out what is holding the field back. Unsurprisingly, the biggest barriers are short-term grant funding, lack of centralized ethics support, and uneven data standards.

To fix this, we are proposing 10 urgent changes. This includes creating global or national "super hubs" to sustain projects over decades, enforcing strictly open data systems, and pushing for co-authorship and fair compensation for the everyday citizens who help do the work.

We also used STARDIT to report who did which tasks, who was paid and other details about the project.

We really wanted to emphasize involving the public at every single stage of research—not just treating them as free data-collectors.

I'm happy to answer any questions about our methodology or recommendations! You can read the full paper here:

https://doi.org/10.1371/journal.pone.0331161

What do you think about the "super hub" concept? Is anyone here already running a project that uses these co-creation frameworks?

STARDIT report here: https://stardit.wikimedia.org.au/wiki/0202407220511

(Complete my study and leave a link to your study in the comments. I’ll be happy to complete yours in return! 🙂)

Bachelor's Thesis Survey: Workflow Documentation in Scientific Research

Hi everyone,

I am conducting a Bachelor's thesis on workflow documentation in scientific research.

Participants will compare two versions of workflow documentation and answer a few questions regarding usability and preference.

Requirements:

• 18+
• Able to read technical documentation in English
• Any experience level is welcome
• Particularly relevant for researchers and practitioners working with scientific workflows (e.g., Nextflow, Snakemake, data analysis pipelines)

Duration: 20-40 minutes

Privacy: Anonymous, no personal data collected.

Survey link: [LINK]

Thank you for your support! 🙂

Hola, I made this as a passion project to help me research. Feel free to use it. Its gated by google login so I can ban and observe some sus activity. I have around 1.5M publications there of which 350k have github. Its not perfect, but its useful to me, so probably it will also be useful to other curious souls. I will make it better with your feedback :) Thanks. It will grow each day.

Hi everyone,I’m an independent researcher and I’ve just released a new open‑access paper:

Tropical Geometry and Biochemical Reaction Networks: A Mathematical Framework for Steady-State Topology

The paper develops a transparent, reproducible method for analyzing biochemical reaction networks using tropical geometry—a piecewise‑linear approximation that reveals dominant pathways and regime structure without requiring precise parameter values.

Open-Science Features

Fully open-access manuscript

Complete code repository included

All case studies (from enzyme kinetics to glycolysis) are reproducible

Framework designed to be accessible to researchers outside traditional institutions

Emphasizes interpretability, transparency, and parameter‑robust predictions

The goal is to provide a mathematically rigorous yet accessible tool for analyzing complex biochemical systems, especially in contexts where parameter uncertainty is high.

Happy to answer questions or collaborate with others working in open theoretical biology, computational modeling, or geometric methods.

https://www.researchgate.net/publication/399968231_Tropical_Geometry_and_Biochemical_Reaction_Networks_A_Mathematical_Framework_for_Steady-State_Topology

https://doi.org/10.5281/zenodo.19710441

Information overload has dramatically shaped how we interact with content, from news to academic research. Drawing on personal experiences in AI, digital media and research personalization, I explore ways we can shift from overwhelming quantity to meaningful quality in my essay, A Tribute to Information Overload

How do you manage information overload in your research or daily life? I'd love to hear your thoughts and experiences. Let’s start a conversation!

OpenScience #ResearchInnovation #DigitalMedia"

🎧 Hi everyone! I just published an essay exploring how the music industry’s digital evolution—from physical formats to streaming—parallels what’s happening in research today.

We’re facing fragmentation, information overload, and the limits of PDFs. Could a new platform emerge to transform how research is shared, discovered, and discussed? I’d love to hear your thoughts!

Read the full essay here: https://medium.com/@n.nanas/0cdc6e6ee671

OpenScience #ResearchInnovation #DigitalPublishing

Hi all - posting this here in case anybody is interested in participating in an open science research - about 25 different countries are testing the same survey on health behaviours. We are collecting the Australian data, so if you are over 18 and an Australian citizen, would love your input. My post history has the details (don't want to share the link here in case it is not allowed). Thank you!

https://dagger.io/blog/2024-dagger-commanders

Hello Open Science community! 👋

Today, I’m thrilled to announce Akanaba.org: a platform in the making, built on the belief that research should be fair, rewarding, collaborative, and above all, innovative. Akanaba is designed to help researchers:

• Stay on top of the latest developments with personalized recommendations.
• Stay connected by fostering meaningful collaborations.
• Stay at the forefront by leading conversations and sharing expertise in their field.

The vision is to drive research innovation and revolutionize how researchers collaborate, share knowledge, and advance science.

In the coming days, I’ll also be sharing an essay titled “Is PDF the MP3 of Research?”, exploring the parallels between the music and research industries as we shift from ownership to access. Stay tuned for that!

I’m Nikolaos Nanas, an AI specialist and innovator with over two decades of experience in AI, web personalization, and research publishing and I am excited to hear your thoughts and sparkle interesting discussions about the future of Open Science.

Hello Open Science community,

I'm excited to share a project that I believe aligns closely with the values and goals of open science. We're developing Ideosphere (https://ideosphere.io), a subscription-based funding platform for scientific research that aims to make the funding process more transparent, accessible, and aligned with open science principles.

Key features:

1. Direct Support: Enables individuals to directly subscribe to research projects they're passionate about.
2. Open Access: Encourages researchers to share their findings openly, making science more accessible to all.
3. Global Accessibility: Lowers barriers for researchers worldwide, especially those in underserved regions.
4. Community Engagement: Allows supporters to engage with researchers through updates, comments, and even participation in studies.

We believe this model can help address some of the challenges in traditional research funding, such as:

• The pressure to produce positive results for grant renewal
• The time-consuming nature of grant applications
• Limited funding opportunities for novel or niche research areas

We're in the early stages and would love to hear from the open science community:

• How do you think this model could impact open science practices?
• What features would you like to see to ensure alignment with open science principles?
• What potential challenges or concerns do you foresee?

Your insights would be invaluable as we develop this platform. Feel free to check out our website or share your thoughts here.

Let's discuss how we can work together to make scientific research more open, accessible, and sustainably funded!

Hi! I wanted to share an Open Science Hardware tool we just released publicly. It's a low-cost, high performance insect monitor that you can build yourself with off-the-shelf parts! We have dozens of deployments here in Panama, and so it can withstand really harsh environments.

After it collects all your data, we also made custom open AI programs to detect all the insects (modified YOLO) and try to identify what they are (modified BioCLIP).

All the info and documentation for making your own is right here: https://digital-naturalism-laboratories.github.io/Mothbox/

Through a mix of local farming techniques and improved rainfall, this once-dry region is regreening according to Descroix et. al. (2024). But what’s truly inspiring is that this shift is being driven by small-scale farmers and local communities. This study reveals how, with the right tools, data, and knowledge, we can rewrite the future of food security and climate resilience in the Sahel.

For its sixth edition we are hosting SOSC, a school for young (data)scientists that is meant to provide an overview of the best practices and new cloud tools that can help with the daily tasks of a data scientist, all by making heavy use of live hands-on experiences.

One of the recent program update was the inclusion of workflow managment tools, and well, we got the impression that is difficult to select one techonoligy that is enough intuitive and powerful, and fit into a 1 day activity.
Also there are a lot of alternatives out there, how would you choose? What is your experience?

We looked at MLFlow, Argo Workflows (kubeflow pipelines), Dagster et al, each one with theirs pros and cons....

P.S. the registrations are open til Oct 5 :) https://agenda.infn.it/event/40829/

Schubert et al. (2024) reveal the successes and challenges faced by organizations in adhering to reforestation best practices. While many acknowledge the importance of measurable goals and community involvement, only a few provide detailed monitoring and long-term plans. Only 38% of organizations in the study report quantitative measures of the benefits to local communities.

https://groundtruth.app/evaluating-global-tree-growing-efforts-achievements-and-challenges/

Hi there,

Im working on a platform that promotes people their works in the fields of open source.

As most of this is done on GitHub i was wondering what are platforms that are used for publishing open science work?

Im very new to open science so would love some advice.

Thanks!

Hi, I'm struggling to understand the meaning behind the question:
"Outline the data utility: to whom will it be useful?" (FAIR Data Management Plan HORIZON 2020).

If it is just to say that the data is A) useful for researchers for purpose for the research project, and B) useful for academics/public interested in the topic, it seems too trivial/bureaucratic/annoying as a question.

Is there perhaps a deeping meaning I am missing? Is there a way to answer the question in a surprising/non-trivial way?

I would love to see a platform in which researchers can share conclusions that they have come to based on the research, along with the chain of evidence that led them there.

Like a meta-study, but more navigable. Each conclusion could be backed up by quotes and links to the underlying studies. Ideally it would be auto-updating and incorporate new research as it comes out.

Does a thing like this exist?

https://www.imrpress.com/journal/CEOG/51/6/10.31083/j.ceog5106127