exloop 0.1.0__tar.gz → 0.2.0__tar.gz

exloop-0.2.0/.gitignore

@@ -0,0 +1,8 @@
+dist/
+build/
+*.egg-info/
+__pycache__/
+*.pyc
+.ruff_cache/
+.DS_Store
+# hatchling copies this file into the sdist as it is; keep it free of anything private.

{exloop-0.1.0 → exloop-0.2.0}/PKG-INFO

@@ -1,7 +1,9 @@
 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.
+Version: 0.2.0
+Summary: Human-led exploration skills for any AI tool that reads SKILL.md: a persistent map, structured idea comparison, and a zero-dependency state helper.
+Project-URL: Repository, https://github.com/hzshen88/exloop
+Project-URL: Issues, https://github.com/hzshen88/exloop/issues
 Author: hzshen88
 License-Expression: Apache-2.0
 License-File: LICENSE
@@ -17,9 +19,10 @@ Description-Content-Type: text/markdown
 
 **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.
+keeps a map of where you have been, and offers the next step that is within reach. When
+several explanations are in play, Idea Lab helps draw, attack, compare, and check them
+without forcing an early winner. Both ship as skills for any AI tool that reads
+`SKILL.md` files — Claude Code, Codex, and the like.
 
 ## Installing
 
@@ -31,17 +34,17 @@ python -m pip install newlife
 newlife start my-research
 ```
 
-`start` installs the exloop skill, together with newlife's own, into every AI tool found
+`start` installs the exloop and Idea Lab skills, 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')"
+python -c "import exloop; print(exloop.skills_dir())"
 ```
 
-and copy the directory that prints into your AI tool's skills folder
+and copy the skill directories it contains into your AI tool's skills folder
 (`~/.claude/skills/`, `~/.codex/skills/`, ...).
 
 ## Using it
@@ -59,10 +62,16 @@ what measurement would make the answer different — the AI says so once, and on
 hands the record to newlife (`questions/<slug>/origin/`), where the preregistration
 discipline takes over.
 
+Idea Lab is not a second entry point that must be completed first. It is an optional
+reasoning pattern inside exploration. The AI uses it when competing or underspecified
+explanations need to be made explicit, challenged, and distinguished.
+
 ## 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/idea-lab/SKILL.md` with domain profiles for formal theory, empirical and causal
+  research, simulation, engineering and product mechanisms, and interpretive research.
 - `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`.
@@ -70,3 +79,21 @@ discipline takes over.
   files. exloop has no other API and no dependencies.
 
 Requires Python 3.11 or newer.
+
+## This repository
+
+| Path | What it holds |
+|---|---|
+| `skills/exloop/` | The persistent, human-led exploration skill and state helper. |
+| `skills/idea-lab/` | The optional Draw—Attack—Compare—Check reasoning pattern and domain profiles. |
+| `src/exloop/__init__.py` | `skills_dir()`, the one Python function. |
+| `scripts/install-skill.py` | Installs the master byte for byte into AI tool directories; `--force` to overwrite drifted copies. |
+| `scripts/check_release_artifacts.py` | Refuses to ship anything but the skills: run it on `dist/` before `uv publish`. |
+
+```bash
+python3 skills/exloop/scripts/exploration_state.py self-test
+uv build --out-dir dist && python3 scripts/check_release_artifacts.py dist
+```
+
+The skill is used downstream by [newlife](https://github.com/hzshen88/newlife), which
+depends on this package. Apache-2.0.

exloop-0.1.0/README.pypi.md → exloop-0.2.0/README.md

@@ -2,9 +2,10 @@
 
 **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.
+keeps a map of where you have been, and offers the next step that is within reach. When
+several explanations are in play, Idea Lab helps draw, attack, compare, and check them
+without forcing an early winner. Both ship as skills for any AI tool that reads
+`SKILL.md` files — Claude Code, Codex, and the like.
 
 ## Installing
 
@@ -16,17 +17,17 @@ python -m pip install newlife
 newlife start my-research
 ```
 
-`start` installs the exloop skill, together with newlife's own, into every AI tool found
+`start` installs the exloop and Idea Lab skills, 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')"
+python -c "import exloop; print(exloop.skills_dir())"
 ```
 
-and copy the directory that prints into your AI tool's skills folder
+and copy the skill directories it contains into your AI tool's skills folder
 (`~/.claude/skills/`, `~/.codex/skills/`, ...).
 
 ## Using it
@@ -44,10 +45,16 @@ what measurement would make the answer different — the AI says so once, and on
 hands the record to newlife (`questions/<slug>/origin/`), where the preregistration
 discipline takes over.
 
+Idea Lab is not a second entry point that must be completed first. It is an optional
+reasoning pattern inside exploration. The AI uses it when competing or underspecified
+explanations need to be made explicit, challenged, and distinguished.
+
 ## 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/idea-lab/SKILL.md` with domain profiles for formal theory, empirical and causal
+  research, simulation, engineering and product mechanisms, and interpretive research.
 - `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`.
@@ -55,3 +62,21 @@ discipline takes over.
   files. exloop has no other API and no dependencies.
 
 Requires Python 3.11 or newer.
+
+## This repository
+
+| Path | What it holds |
+|---|---|
+| `skills/exloop/` | The persistent, human-led exploration skill and state helper. |
+| `skills/idea-lab/` | The optional Draw—Attack—Compare—Check reasoning pattern and domain profiles. |
+| `src/exloop/__init__.py` | `skills_dir()`, the one Python function. |
+| `scripts/install-skill.py` | Installs the master byte for byte into AI tool directories; `--force` to overwrite drifted copies. |
+| `scripts/check_release_artifacts.py` | Refuses to ship anything but the skills: run it on `dist/` before `uv publish`. |
+
+```bash
+python3 skills/exloop/scripts/exploration_state.py self-test
+uv build --out-dir dist && python3 scripts/check_release_artifacts.py dist
+```
+
+The skill is used downstream by [newlife](https://github.com/hzshen88/newlife), which
+depends on this package. Apache-2.0.

exloop-0.2.0/pyproject.toml

@@ -0,0 +1,43 @@
+[project]
+name = "exloop"
+version = "0.2.0"
+description = "Human-led exploration skills for any AI tool that reads SKILL.md: a persistent map, structured idea comparison, and a zero-dependency state helper."
+readme = "README.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 = []
+
+[project.urls]
+Repository = "https://github.com/hzshen88/exloop"
+Issues = "https://github.com/hzshen88/exloop/issues"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+# The masters are under skills/ at the repository top, the copies people read and edit; the
+# wheel carries byte copies under exloop/skills/, located via `import exloop; exloop.skills_dir()`.
+# newlife's `skills install` uses that to install the exploration skills 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"
+"skills/idea-lab" = "exloop/skills/idea-lab"
+
+# The sdist uses only-include, not include: include patterns are gitignore-style and unanchored,
+# so "README.md" would match every README.md in the tree. 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", "skills/idea-lab", "README.md", "LICENSE", "pyproject.toml"]

{exloop-0.1.0 → exloop-0.2.0}/skills/exloop/SKILL.md

@@ -103,6 +103,30 @@ exactly how one exploration in 2026-08 ended up in three directories.
    boundaries. They are proposals, not a menu the person must select. A new
    judgment or fact from the person may legitimately redirect the exploration.
 
+## When several explanations are live
+
+**REQUIRED SUB-SKILL:** Use `idea-lab` when one observation supports two or more
+plausible mechanisms, the person asks to compare explanations, or a favored story
+needs alternatives before formal framing.
+
+Idea Lab is a reasoning pattern inside this exploration, not a stage before or
+after exloop. Do not ask the person to choose between them, start a second
+exploration, or make them complete a four-step worksheet. Exloop continues to own
+the conversation, persistent state, pivots, and handoff; Idea Lab supplies the
+Draw—Attack—Compare—Check structure one useful edge at a time.
+
+In sustained mode, project its useful changes into the existing map rather than
+inventing a parallel ledger:
+
+- a live candidate explanation is a `node`;
+- a missing discriminator or unsupported premise is `stuck`;
+- a mechanism that survives and transfers is a `framework`;
+- a rejected route, with its reason, is `abandoned`;
+- a reversal or unexpected connection is a `surprise`.
+
+Do not mark every row of an Idea Lab board. Preserve only changes that matter to
+future conversation.
+
 ## Human control and pivots
 
 - Never change the exploration target merely because another direction looks
@@ -165,6 +189,15 @@ 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.
 
+**The line is not "do not look at data".** Exploration looks at data — that is its job, and
+a hypothesis grown out of what you saw is exactly what it is meant to produce. The line
+falls one step later: once the question is handed off, **the hypothesis and the direction
+you expect must be written down before the pilot runs**, because the pilot looks at every
+quantity a criterion names and may hand you the answer before anything is frozen. Changing
+the hypothesis after that point is HARKing, even though changing it before was the method.
+`newlife-goal` §3 says what must be fixed by then; the second half of `newlife-prereg`
+rule one says what to do when the pilot has already answered the main criterion.
+
 ## Authorization boundary
 
 This skill changes conversational behavior and, in sustained mode, writes only

exloop-0.2.0/skills/idea-lab/SKILL.md

@@ -0,0 +1,178 @@
+---
+name: idea-lab
+description: Use when an open-ended research, mechanism, or design question has competing or underspecified explanations and the person is not ready for formal framing or execution. Not for direct factual answers, implementation, debugging, or confirmatory analysis.
+---
+
+# Idea Lab
+
+Use **Draw—Attack—Compare—Check** to turn an intuition into a small portfolio of explanations
+whose differences can be discussed and eventually tested. This is an exploratory
+reasoning pattern, not an evidence-producing or confirmatory workflow.
+
+The person owns the question, target, and consequential choices. Do not replace
+their original idea merely because another route is easier to formalize.
+
+## Fit with the exploration workflow
+
+- For a short exchange, use this pattern in conversation only.
+- **REQUIRED SUB-SKILL:** Use `exloop` when the person asks for sustained
+  exploration, a persistent map, or a handoff into a research repository.
+- Use `surveying-prior-work` when source verification, prior art, or a novelty
+  judgment becomes material.
+- Hand off to `newlife-goal` only when the person can say what observation or
+  measurement would make the answer different.
+
+“Plan the next step” means the next exploratory discriminator while this skill is
+active. It does not by itself authorize a transition into study design,
+preregistration, implementation, or intervention. Name the possible handoff and
+let the person choose it.
+
+Anything observed, computed, or read during Idea Lab is exploratory and therefore
+*seen* for any later preregistration. This skill never freezes a hypothesis, runs a
+confirmatory analysis, or promotes an explored result to confirmation.
+
+## Choose the domain profile
+
+Classify by the dominant inferential risk, not by the researcher's department.
+Read only the one profile that fits:
+
+- [formal theory](references/formal-theory.md);
+- [empirical or causal research](references/empirical-causal.md);
+- [simulation or computational research](references/simulation-computational.md);
+- [engineering or product mechanisms](references/engineering-product.md);
+- [interpretive or historical research](references/interpretive-historical.md);
+- [generic mechanism exploration](references/generic.md) when none dominates.
+
+If two profiles genuinely apply, state the boundary and use only the relevant
+checks from each. Do not duplicate the whole workflow.
+
+## Draw — make the alternatives explicit
+
+Preserve the person's idea as one candidate. Add only enough alternatives to
+expose the consequential uncertainty—usually two to four live candidates, never
+cosmetic rewrites of the same story.
+
+For each candidate, make explicit:
+
+- the claim in one sentence;
+- the mechanism chain: what changes what;
+- necessary assumptions;
+- an expected pattern if it is right;
+- a boundary or observation that would weaken it.
+
+Include a reversed mechanism, selection effect, measurement artifact, or null
+explanation when one is genuinely plausible. Do not manufacture symmetry merely
+to fill a list.
+
+## Attack — challenge before repairing
+
+Attack each candidate on its own terms. Ask for the cheapest decisive weakness:
+a counterexample, violated invariant, hidden assumption, scope boundary, rival
+mechanism, or artifact that produces the same observation.
+
+Keep the roles separate:
+
+1. state the strongest version of the candidate;
+2. attack that version;
+3. classify the damage as contradiction, unsupported premise, limited scope, or
+   unresolved;
+4. repair only if the repair yields a new consequence that was not built into it.
+
+Do not erase failed routes. Record why they failed so they are not rediscovered
+later. A repair that merely fits the motivating observation is curve-fitting, not
+progress.
+
+## Compare — seek discriminators, not a winner
+
+Compare candidates at the point where they predict different observations,
+timings, interventions, counterfactuals, or failure signatures. Prefer the
+cheapest observation that can make one route lose while another survives.
+
+Do not rank explanations as “most likely” without evidence tied to the current
+case. General plausibility, familiarity, theoretical elegance, and labels such as
+“typical amplifier” are not case evidence. If the person asks for a ranking that
+the available evidence cannot support, refuse the ranking and state the first
+observation that would change it. Do not invent numerical thresholds.
+
+Candidates need not be mutually exclusive. When one is a trigger and another an
+amplifier, represent their composition and identify evidence for each link rather
+than forcing a single winner.
+
+## Check — audit provenance and claimed novelty
+
+Maintain these statuses for material claims:
+
+| Status | Meaning |
+|---|---|
+| `user` | Supplied by the person |
+| `observed` | Directly seen in a source, code, data, or run |
+| `established` | Supported by verified prior work |
+| `inferred` | Reasoned from stated premises but not independently verified |
+| `unverified` | Plausible factual claim awaiting a source |
+| `candidate-novelty` | A potentially new combination or claim, not yet established as novel |
+
+“No source found” never means “novel.” This skill does not itself authorize web
+research, data access, repository edits, or experiments; use the authority in the
+person's request and the appropriate skill.
+
+## Run it as a loop, not a four-part lecture
+
+Advance one useful edge per conversational turn. Do not dump every candidate,
+attack, comparison, source question, study design, and preregistration plan at
+once. “Help me explore” or “plan the next step” is not a request for a full board;
+reserve that for an explicit request for a synthesis, matrix, or complete map.
+
+After identifying the first useful discriminator, stop at that boundary. Do not
+specify randomization, estimators, sample sizes, success thresholds, or a frozen
+hypothesis unless the person explicitly chooses to leave Idea Lab for formal
+framing or design.
+
+Loop back when:
+
+- an attack changes a candidate's mechanism;
+- candidates make the same observable prediction;
+- prior work collapses a supposed distinction;
+- a new observation opens a materially different route.
+
+Stop adding branches when four or five live routes are open, or when several turns
+add routes without choosing, resolving, or retiring one. Inventory instead.
+
+## Compact board for synthesis or handoff
+
+When the person asks for a synthesis, or a boundary is ready for `newlife-goal`,
+render only what has actually been developed:
+
+```markdown
+## Current question
+<question and scope>
+
+## Candidate routes
+| Route | Mechanism | Necessary assumptions | Expected pattern | Status |
+
+## Attack ledger
+| Route | Strongest attack | Damage | Repair or reason retained |
+
+## Discriminators
+| Observation or intervention | Route A predicts | Route B predicts | Seen or unobserved |
+
+## Source ledger
+| Claim | Provenance status | Source or missing check |
+
+## Open boundary
+<the one missing distinction, fact, or judgment that most changes the next step>
+```
+
+The board is a map, not a scorecard. Preserve incompatible live routes, abandoned
+routes, and unresolved provenance. End with one reachable next edge, not a verdict.
+
+## Self-check
+
+- Did the person's original idea remain visible?
+- Are the candidates mechanistically different rather than differently worded?
+- Did every surviving route face a real attack?
+- Is there at least one discriminator, or an explicit statement that none is known?
+- Are trigger and amplifier separated where relevant?
+- Are factual support, inference, and possible novelty visibly distinct?
+- Did the exploration avoid inventing a threshold or jumping into confirmation?
+- If asked to rank, was the ranking supported by current case evidence rather than
+  a generic story about what is common?

exloop-0.2.0/skills/idea-lab/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Idea Lab"
+  short_description: "Explore ideas through draw, attack, compare, check"
+  default_prompt: "Use $idea-lab to turn this intuition into competing explanations and find what would distinguish them."

exloop-0.2.0/skills/idea-lab/references/empirical-causal.md

@@ -0,0 +1,19 @@
+# Empirical and causal research profile
+
+**Draw:** population, unit, exposure or treatment, outcome construct, time order,
+estimand, and a causal graph or verbal equivalent. Keep data-generating mechanisms
+separate from measurement mechanisms.
+
+**Attack:** confounding, reverse causation, selection, attrition, interference,
+measurement non-equivalence, post-treatment conditioning, researcher degrees of
+freedom, and external-validity limits.
+
+**Compare:** observations that distinguish mechanisms—timing, negative controls,
+heterogeneous predictions, natural or randomized variation, and measurements that
+do not reuse the motivating outcome. At this stage, identify the discriminator;
+do not turn it into a full design.
+
+**Check:** label all already-viewed outcomes as seen. Do not turn an exploratory
+chart into a confirmatory direction on the same data. When the person chooses to
+move toward testing, use fresh or protected evidence under the preregistration
+workflow.

exloop-0.2.0/skills/idea-lab/references/engineering-product.md

@@ -0,0 +1,17 @@
+# Engineering and product mechanism profile
+
+**Draw:** users or components, state transitions, interfaces, timing, feedback
+loops, incentives, and observability. Separate initiating faults from propagation
+and amplification.
+
+**Attack:** race conditions, stale state, correlated clients, retries, partial
+failure, telemetry gaps, survivorship, rollout interaction, and mitigation that
+masks rather than identifies the cause.
+
+**Compare:** event ordering, trace signatures, invariants, controlled fault
+injection, canaries, and reversible changes. A safe mitigation may be worthwhile
+without proving the root cause; label those outcomes separately.
+
+**Check:** ground claims in the actual request path, logs, code, and deployed
+configuration. Do not infer probability from a generic failure pattern and do not
+invent a success threshold from intuition.

exloop-0.2.0/skills/idea-lab/references/formal-theory.md

@@ -0,0 +1,16 @@
+# Formal theory profile
+
+**Draw:** primitives, actors, information, timing, feasible actions, objectives,
+solution concept, and predicted comparative statics. Seek minimal models that
+differ in one consequential assumption.
+
+**Attack:** consistency of primitives; existence and multiplicity; hidden
+regularity assumptions; degenerate cases; sign reversals; whether the claimed
+result is encoded directly in an assumption; counterexamples at the boundary.
+
+**Compare:** theorem statements, counterexamples, comparative statics, welfare
+ranking, or a prediction that survives when a disputed assumption is relaxed.
+
+**Check:** distinguish a known theorem, an adaptation of an established model, a
+new proof route, and a candidate-new proposition. Mathematical validity and
+literature novelty are separate questions.

exloop-0.2.0/skills/idea-lab/references/generic.md

@@ -0,0 +1,14 @@
+# Generic mechanism profile
+
+Use when no specialized inferential risk dominates.
+
+**Draw:** actors or objects, state, mechanism chain, assumptions, expected change.
+
+**Attack:** missing link, reverse direction, common cause, boundary case,
+measurement artifact, or a null process that yields the same observation.
+
+**Compare:** identify a timing, intervention, counterfactual, or failure signature
+on which the candidates diverge.
+
+**Check:** separate what the person supplied, what was observed, what was inferred,
+and what remains unverified.

exloop-0.2.0/skills/idea-lab/references/interpretive-historical.md

@@ -0,0 +1,16 @@
+# Interpretive and historical research profile
+
+**Draw:** candidate interpretations, relevant actors, chronology, proposed motives
+or structures, scope, and the source base each interpretation needs.
+
+**Attack:** anachronism, source dependence, archival silence, survivorship,
+translation or category drift, hindsight, and whether the account explains only
+selected cases.
+
+**Compare:** contradictory primary sources, chronology, coverage of difficult
+cases, assumptions required, and whether one interpretation explains evidence the
+other treats as exceptional.
+
+**Check:** record source type, date, authorship, transmission, independence, and
+contestation. Do not force statistical falsifiability onto a conceptual or
+interpretive claim; demand source-sensitive constraints instead.

exloop-0.2.0/skills/idea-lab/references/simulation-computational.md

@@ -0,0 +1,16 @@
+# Simulation and computational research profile
+
+**Draw:** entities, state variables, update rules, scheduler, environment,
+stochasticity, scale, initialization, and observables. Separate properties imposed
+by construction from behavior decided by running.
+
+**Attack:** implementation artifact, scheduler dependence, initial-condition
+dependence, finite-size effect, seed instability, parameter tuning, insufficient
+power, invalid proxy, and a control that cannot actually turn red.
+
+**Compare:** analytic limits, matched controls, mechanism ablations, sensitivity
+surfaces, seed ensembles, scaling behavior, and out-of-calibration predictions.
+
+**Check:** every number must be traceable to an artifact and configuration. Runs
+inside Idea Lab are exploratory and seen; they cannot later serve as blind
+confirmation.

{exloop-0.1.0 → exloop-0.2.0}/src/exloop/__init__.py

@@ -1,11 +1,11 @@
 """exloop — human-led exploration with a persistent map.
 
 This package exists so that installing newlife (which will depend on it) puts the
-exloop skill on the machine without a trip to GitHub. It ships the skill files
+exploration skills on the machine without a trip to GitHub. It ships the skill files
 and the zero-dependency state helper the skill uses, and nothing else. newlife never
 imports exloop's code: the interface between the two is files — `handoff` writes into a
-newlife question's `origin/`. The skill master is `skills/exloop/` in the exloop
-repository; the wheel carries a byte copy under `exloop/skills/`.
+newlife question's `origin/`. The skill masters are under `skills/` in the exloop
+repository; the wheel carries byte copies under `exloop/skills/`.
 """
 
 from __future__ import annotations
@@ -16,7 +16,7 @@ __all__ = ["skills_dir"]
 
 
 def skills_dir() -> Path:
-    """The directory holding the skill masters (`exloop/SKILL.md` and friends).
+    """The directory holding the skill masters (`exloop/`, `idea-lab/`, and friends).
 
     In an installed wheel it is `exloop/skills/`, force-included at build time. In an
     editable checkout the files are the repository's own `skills/`, two levels up from this

exloop-0.1.0/.gitignore

@@ -1,20 +0,0 @@
-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/pyproject.toml

@@ -1,44 +0,0 @@
-[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).