exloop 0.1.0__tar.gz

exloop-0.1.0/.gitignore

@@ -0,0 +1,20 @@
+node_modules/
+dist/
+build/
+*.egg-info/
+*.log
+.DS_Store
+__pycache__/
+.ruff_cache/
+*.pyc
+.gstack/
+
+# Local scratch and tool caches, never versioned
+tmp/
+output/
+.workbuddy/
+AGENTS.md
+
+# hatchling copies this file into the sdist as it is, so no path under the sealed
+# exploration archive is named here; per-exploration derived caches (npz, wiki caches)
+# are listed in the local .git/info/exclude instead.

exloop-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

exloop-0.1.0/PKG-INFO

@@ -0,0 +1,72 @@
+Metadata-Version: 2.5
+Name: exloop
+Version: 0.1.0
+Summary: Human-led exploration with a persistent map: the exloop skill for any AI tool that reads SKILL.md, plus the zero-dependency state helper it uses.
+Author: hzshen88
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: claude-code,codex,exploration,human-in-the-loop,research-questions,skill
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# exloop
+
+**Human-led exploration with a persistent map.** An AI companion that does not answer
+your question for you: it asks one or two honing questions, walks one edge at a time,
+keeps a map of where you have been, and offers the next step that is within reach. It
+ships as a skill for any AI tool that reads `SKILL.md` files — Claude Code, Codex, and
+the like.
+
+## Installing
+
+Most people get exloop by installing [newlife](https://pypi.org/project/newlife/), which
+depends on it:
+
+```bash
+python -m pip install newlife
+newlife start my-research
+```
+
+`start` installs the exloop skill, together with newlife's own, into every AI tool found
+on the machine.
+
+On its own:
+
+```bash
+python -m pip install exloop
+python -c "import exloop; print(exloop.skills_dir() / 'exloop')"
+```
+
+and copy the directory that prints into your AI tool's skills folder
+(`~/.claude/skills/`, `~/.codex/skills/`, ...).
+
+## Using it
+
+Open a folder in your AI tool and say:
+
+> Explore this with me: *your curiosity*
+
+The AI asks; you answer and decide. The map is kept silently in
+`~/.exloop/explorations/<slug>/`, one folder per exploration — the same folder whichever
+AI tool you switch to, because the identity is the slug, not the chat session. When you
+close an exploration the AI archives the record into your research repository
+(`explorations/<slug>/`). When a boundary has become a decidable question — you can say
+what measurement would make the answer different — the AI says so once, and on your yes
+hands the record to newlife (`questions/<slug>/origin/`), where the preregistration
+discipline takes over.
+
+## What is in the package
+
+- `skills/exloop/SKILL.md` with its references: the protocol (four events — started,
+  marked, pivoted, closed — and the map as their projection) and the state model.
+- `skills/exloop/scripts/exploration_state.py`: the zero-dependency helper the skill
+  runs — `init`, `mark`, `pivot`, `show`, `close`, `list`, `archive`, `handoff`, and a
+  `self-test`.
+- `exloop.skills_dir()`: the one Python function, so that newlife can locate the skill
+  files. exloop has no other API and no dependencies.
+
+Requires Python 3.11 or newer.

exloop-0.1.0/README.pypi.md

@@ -0,0 +1,57 @@
+# exloop
+
+**Human-led exploration with a persistent map.** An AI companion that does not answer
+your question for you: it asks one or two honing questions, walks one edge at a time,
+keeps a map of where you have been, and offers the next step that is within reach. It
+ships as a skill for any AI tool that reads `SKILL.md` files — Claude Code, Codex, and
+the like.
+
+## Installing
+
+Most people get exloop by installing [newlife](https://pypi.org/project/newlife/), which
+depends on it:
+
+```bash
+python -m pip install newlife
+newlife start my-research
+```
+
+`start` installs the exloop skill, together with newlife's own, into every AI tool found
+on the machine.
+
+On its own:
+
+```bash
+python -m pip install exloop
+python -c "import exloop; print(exloop.skills_dir() / 'exloop')"
+```
+
+and copy the directory that prints into your AI tool's skills folder
+(`~/.claude/skills/`, `~/.codex/skills/`, ...).
+
+## Using it
+
+Open a folder in your AI tool and say:
+
+> Explore this with me: *your curiosity*
+
+The AI asks; you answer and decide. The map is kept silently in
+`~/.exloop/explorations/<slug>/`, one folder per exploration — the same folder whichever
+AI tool you switch to, because the identity is the slug, not the chat session. When you
+close an exploration the AI archives the record into your research repository
+(`explorations/<slug>/`). When a boundary has become a decidable question — you can say
+what measurement would make the answer different — the AI says so once, and on your yes
+hands the record to newlife (`questions/<slug>/origin/`), where the preregistration
+discipline takes over.
+
+## What is in the package
+
+- `skills/exloop/SKILL.md` with its references: the protocol (four events — started,
+  marked, pivoted, closed — and the map as their projection) and the state model.
+- `skills/exloop/scripts/exploration_state.py`: the zero-dependency helper the skill
+  runs — `init`, `mark`, `pivot`, `show`, `close`, `list`, `archive`, `handoff`, and a
+  `self-test`.
+- `exloop.skills_dir()`: the one Python function, so that newlife can locate the skill
+  files. exloop has no other API and no dependencies.
+
+Requires Python 3.11 or newer.

exloop-0.1.0/pyproject.toml

@@ -0,0 +1,44 @@
+[project]
+name = "exloop"
+version = "0.1.0"
+description = "Human-led exploration with a persistent map: the exloop skill for any AI tool that reads SKILL.md, plus the zero-dependency state helper it uses."
+# The repository README.md is the author's own (Chinese, linking into private directories); PyPI gets its own page.
+readme = "README.pypi.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+authors = [{ name = "hzshen88" }]
+keywords = ["exploration", "research-questions", "skill", "claude-code", "codex", "human-in-the-loop"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Science/Research",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+]
+dependencies = []
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+# The master is skills/exloop/ at the repository top, the copy people read and edit; the wheel
+# carries a byte copy under exloop/skills/, located via `import exloop; exloop.skills_dir()`.
+# newlife's `skills install` uses that to install the exploration skill alongside its own,
+# without importing any exloop code.
+[tool.hatch.build.targets.wheel]
+packages = ["src/exloop"]
+
+[tool.hatch.build.targets.wheel.force-include]
+"skills/exloop" = "exloop/skills/exloop"
+
+# The sdist uses only-include, not include: include patterns are gitignore-style and unanchored,
+# so "README.md" matches every README.md in the tree — on 2026-09-06 that pulled the READMEs of
+# 13 sealed explorations, docs/science-superpowers and vendor into the sdist. only-include takes
+# exactly these paths. scripts/check_release_artifacts.py compares the built artifacts file by
+# file and must pass before anything is published.
+[tool.hatch.build.targets.sdist]
+only-include = ["src/exloop", "skills/exloop", "README.pypi.md", "LICENSE", "pyproject.toml"]
+exclude = [".gitignore"]
+
+# No [project.urls]: the source repository is private and a public reader cannot open it. Point
+# here at the clean public repository once it exists (README.md, the paragraph on going public).

exloop-0.1.0/skills/exloop/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: exloop
+description: Use when a person wants to explore an open-ended curiosity, sharpen a vague question through sustained dialogue, or preserve a map of changing hypotheses and unresolved boundaries; do not use for direct factual answers, implementation, debugging, or confirmatory analysis.
+---
+
+# Exploration Loop
+
+> **Commands in this file are for you, the assistant, to run; the person decides.**
+> Asked how this works or where they are, describe what *they* do — see the `newlife` skill.
+
+Help the person turn a curiosity into a better question, a map of what changed,
+and reusable ways of thinking. The person owns the target and every consequential
+choice. The assistant supplies names, mechanisms, counterexamples, evidence, and
+reachable next directions without taking over the exploration.
+
+> **This file is the master, kept in the exloop repository under
+> `skills/exloop/`.** The copies under `~/.claude/skills/`,
+> `~/.codex/skills/` and `~/.workbuddy/skills/` are installed verbatim by
+> `scripts/install-skill.py`; nothing in this skill depends on which tool is
+> running it. Two host-specific copies once drifted apart (they differed only in
+> the host's name and the state directory), which is why the master exists.
+
+## Select the mode
+
+- Use **sustained mode** when the person explicitly invokes this skill, asks to
+  keep a map, or wants an exploration that may span several turns. Read
+  [references/state-model.md](references/state-model.md) and keep file-backed
+  state outside the working repository.
+- Use **conversation-only mode** for a short exploratory exchange. Apply the
+  protocol without creating files.
+- Do not convert a request for a direct answer, code change, diagnosis, review,
+  or confirmatory analysis into an exploration. Answer or use the appropriate
+  workflow instead.
+
+Before the first substantive reply, read
+[references/protocol.md](references/protocol.md). It contains the interaction
+rules and the observed failure modes this skill must resist.
+
+## Before the first exploration in a research repository: set things up yourself
+
+The person should never have to type a shell command. If the conversation is happening
+inside a research repository (or the person wants their explorations and questions kept
+somewhere), do the setup for them, telling them in one line what you are doing:
+
+1. `newlife` missing from PATH? Install it: `uv tool install newlife` (fallback:
+   `pipx install newlife`, then `python3 -m pip install --user newlife`). It brings the
+   `exloop` package along, so this skill's helper and the two newlife skills arrive too.
+2. Not yet a research repository (no `NEXT.md`)? Run `newlife start .` in it — git init,
+   `.gitignore`, `NEXT.md`, and the skills installed into every AI tool found. If it
+   reports a missing git identity, ask the person for a name and email once and set them.
+3. Then continue as below. Every later command — `newlife init`, `pilot`, `freeze`, `run`,
+   `check`, `audit`, this skill's `archive` and `handoff` — is yours to run at the moment
+   the skills say so; the person only decides.
+
+Say what you installed and where; never install anything else on the strength of this.
+
+## What you make while exploring goes into the research repository, not a temp directory
+
+Explorations run code: a paper gets converted to text, a repository gets cloned, a synthetic
+experiment gets written and run, a table gets downloaded. Measured on the first real
+exploration after this skill shipped: 542 MB of exactly that sat in the session's scratch
+directory, and the numbers it produced were on the map and in `goal.md` — traceable to
+nothing once the session ended.
+
+So, as soon as a research repository is known, keep everything you produce under
+`<repo>/explorations/<slug>/artifacts/`: scripts (with how to run them in the docstring),
+small results (JSON, tables, figures), the extracted text of a paper you are quoting. Big
+things you can fetch again (a cloned repository, a virtualenv, raw data over a few MB) may
+stay outside, but the fetch command and the commit or version go into a `README.md` or a
+manifest there. `archive` later adds `process/` and the entry README beside it; `handoff`
+does not copy artifacts — the question's `origin/README.md` points at them. The rule the
+archive convention states is the one you are serving: **every number on the map must be
+traceable to a file.**
+
+## One exploration, one slug, any tool
+
+In sustained mode the exploration is identified by a **slug**, not by the
+session. Pick it at `init`, silently, the way an archive folder is named:
+`YYYY-MM-DD-<two-to-four-english-words>`, date = the day the exploration
+started, words = the question, never the expected conclusion. State lives in
+`~/.exloop/explorations/<slug>/` whatever tool is in use, so the person can
+continue the same exploration in Claude Code, Codex or WorkBuddy without the
+record splitting. To resume, run `list` to find the slug, then `show --id <slug>`
+before replying. **Never derive the id from a thread or session id**: that is
+exactly how one exploration in 2026-08 ended up in three directories.
+
+## Core loop
+
+1. **Hone the question.** If the curiosity is vague, ask one high-leverage
+   question and offer a sharper restatement. Ask at most two rounds. If the
+   person says to start, stop honing immediately.
+2. **Advance one edge.** Add one mechanism, distinction, counterexample, or
+   piece of evidence—not a complete lecture. Match complexity to the person's
+   language and corrections.
+3. **Name what is forming.** When the person offers an inchoate judgment from
+   experience, give it a short reusable name and connect it to a mechanism.
+4. **Challenge the claim, not the person.** Restate the claim before testing it.
+   Prefer: “What would change your mind?” The answer creates a shared criterion;
+   the assistant does not become the judge.
+5. **Update the map silently.** Record zero to three meaningful changes per
+   turn. Do not ask the person to keep notes or use special commands.
+6. **Offer reachable directions.** Draw one to three next directions from open
+   boundaries. They are proposals, not a menu the person must select. A new
+   judgment or fact from the person may legitimately redirect the exploration.
+
+## Human control and pivots
+
+- Never change the exploration target merely because another direction looks
+  easier or more productive.
+- When the person explicitly changes the target, record the pivot and why while
+  preserving the root question.
+- When a pivot is inferred only during retrospective review, mark it as detected;
+  never present it as something the person explicitly said.
+- Low uptake of the assistant's proposed directions is healthy. It often means
+  the person is supplying the exploration's new facts rather than following the
+  assistant's track.
+
+## Convergence and closure
+
+A boundary has become a candidate for newlife the moment the person can say
+**what measurement would make the answer different**. When that happens, say so
+once — "this one could be settled; want to hand it to newlife?" — and let the
+person decide. Do not push; an exploration is not a funnel.
+
+If four or five directions are open, or no direction has been chosen or retired
+for two or three turns, stop adding branches. Inventory what is understood, the
+reusable frameworks, and the live boundaries; then ask what container or output
+the person wants.
+
+When the person asks to stop, summarize, or turn the exploration into an
+artifact:
+
+- render the current map;
+- separate conclusions, reusable frameworks, unresolved boundaries, abandoned
+  paths, surprises, and pivots;
+- state what evidence was observed versus inferred;
+- record closure in sustained mode (`close`), then copy the record into the
+  person's **research repository** — the one `newlife start` created, the one
+  that holds `questions/` — with `archive --repo <research repo>`: it lands in
+  `explorations/<slug>/process/` there, and the first time it also writes the
+  four-section `README.md` skeleton and an empty `artifacts/`. The archive folder
+  carries the same slug as the workbench, so the two never disagree about which
+  exploration this was. The record does **not** go into the exloop repository;
+- if the exploration produced a question the person wants to freeze and judge in
+  newlife, three commands in this order: `newlife init <slug>` inside the research
+  repository (same slug; it scaffolds `questions/<slug>/` with an `origin/`), then
+  `handoff --repo <research repo>` (it refuses if `init` has not run — writing
+  first would make `init` refuse instead), then invoke the `newlife-goal` skill.
+  If the exploration continues after the handoff, the copy in `origin/` is a snapshot;
+  re-run `handoff --repo … --force` when the record has grown, or rely on `archive` at
+  closure. `handoff` copies the same record into `questions/<slug>/origin/` and writes
+  `goal-draft.md`, a `goal.md`-shaped draft with
+  §1 (where the question came from: root question, pivots and why, surprises,
+  frameworks), §3 (abandoned paths) and §4 (open boundaries) pre-filled from the
+  map. The six anchors stay TODO: they are `newlife-goal`'s job, and nothing
+  in a map can supply a counterparty;
+- do not rate the person, rank the exploration, or declare the chosen direction
+  objectively correct.
+
+## Research boundary
+
+Exploration can generate hypotheses, but it cannot retroactively make an
+analysis confirmatory. Before inspecting outcomes for a confirmatory claim,
+switch to a workflow that locks the hypothesis, analysis, prediction, and
+decision rule first. Label anything already inspected as exploratory. Anything
+run during the exploration counts as *seen* for a later preregistration.
+
+## Authorization boundary
+
+This skill changes conversational behavior and, in sustained mode, writes only
+to its state directory under `~/.exloop/explorations/` (and, on an explicit
+`archive` or `handoff`, into the research repository named by `--repo` or the
+directory named by `--to`). It does not by itself authorize
+web research, repository edits, external messages, purchases, or other side
+effects.

exloop-0.1.0/skills/exloop/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Exploration Loop"
+  short_description: "Human-led exploration with a persistent map"
+  default_prompt: "Use $exloop to explore this question with me and preserve what changes."