exoma 0.1.0__tar.gz

exoma-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 2026 dammar01
+
+   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.

exoma-0.1.0/PKG-INFO

@@ -0,0 +1,313 @@
+Metadata-Version: 2.4
+Name: exoma
+Version: 0.1.0
+Summary: Evidence-driven problem solving for AI agents: context management, delegated exploration, and evidence gathering around the agent that reasons and decides.
+Keywords: ai-agents,coding-agents,claude-code,delegation,evidence,context-management,llm
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development
+Requires-Dist: playwright==1.60.0 ; extra == 'e2e'
+Requires-Python: >=3.10
+Project-URL: Repository, https://github.com/dammar01/Exoma
+Provides-Extra: e2e
+Description-Content-Type: text/markdown
+
+<div align="center">
+
+<img src="https://raw.githubusercontent.com/dammar01/Exoma/main/docs/assets/banner.svg" alt="Exoma — Evidence-driven problem solving for AI agents. Context over prescription. Evidence over expectation. Effective coordination over unnecessary complexity." width="900">
+
+# Exoma
+
+**Evidence-driven problem solving for AI agents.**
+
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Python](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![Dependencies](https://img.shields.io/badge/dependencies-none-brightgreen.svg)](docs/installation.md#requirements)
+[![PyPI](https://img.shields.io/badge/pip-exoma-blue.svg)](docs/installation.md)
+[![Version](https://img.shields.io/badge/version-0.1.0-informational.svg)](CHANGELOG.md)
+
+**[Installation guide](docs/installation.md)** · [Security](docs/security.md) · [Team guide](docs/team-guide/README.md) · [Reference](docs/reference.md)
+
+</div>
+
+---
+
+## What is Exoma?
+
+Exoma is a library that supports problem solving by AI agents through context management,
+exploration, tool use, work delegation, and evidence gathering.
+
+It starts from the idea that how well an AI solves a problem is not decided by the model
+alone, but also by how information is provided, how work is organized, and how the results
+of an investigation are evaluated.
+
+A person who hands a problem to an AI should not have to prescribe every step, or steer it
+toward a conclusion they already had in mind. The person sets the goal, the initial context,
+and the constraints; the AI then uses the capabilities and resources available to it to
+investigate the problem, weigh the possibilities, and reach a solution grounded in evidence.
+
+Exoma supports that process as an external system that organizes the flow of context, work,
+and information between an AI agent and the resources it uses.
+
+---
+
+## Core philosophy
+
+**People define the problem, not the answer to be found.**
+
+An AI is not only expected to produce the answer a person asked for. It also needs room to
+check assumptions, weigh alternatives, find what was not yet known, and reach a conclusion
+that may differ from what whoever assigned the task expected.
+
+Exoma focuses on three principles:
+
+1. **Context over prescription.** Provide the relevant context and resources so the AI can
+   investigate the problem, rather than over-specifying the steps and conclusions it must
+   follow.
+2. **Evidence over expectation.** Favor problem solving grounded in evidence and evaluation,
+   not in confirming a person's assumptions.
+3. **Effective coordination over unnecessary complexity.** Organize agents, tools, and
+   compute by what the task needs, without assuming that more agents or more process always
+   produce better quality.
+
+These principles are a design direction to be realized and evaluated through the
+implementation, not a guarantee that any AI agent will always be objective or correct.
+
+---
+
+## How Exoma works
+
+Technically, Exoma is a supporting layer around an AI agent. Depending on the need and the
+implementation, it can manage context retrieval, delegate exploration to another agent,
+gather evidence from external sources, retain relevant information, and control the flow of
+execution.
+
+The AI agent still does the semantic reasoning and makes the decisions its role calls for.
+Exoma organizes the processes and resources that support that work. The aim is not to
+replace the model or to make the whole process fully automatic; it is to let the AI complete
+a task more effectively without a person directing every step or conclusion.
+
+The current implementation targets **coding agents**, with Claude Code as the primary agent.
+It is installed as a Python package (`pip install exoma`) with a CLI (`exoma`), and separates
+work that needs **broad repository inspection** from work that needs the **primary agent's
+reasoning and implementation context**. A coding agent on a mature repository spends much of
+its effort locating modules, tracing call sites, and reading conventions before it changes
+anything; Exoma moves that inspection into a separate execution context and returns
+structured evidence: a digest, `file:line` anchors, and a reference to the full evidence on
+disk.
+
+<p align="center">
+<img src="https://raw.githubusercontent.com/dammar01/Exoma/main/docs/assets/architecture.svg" alt="Exoma architecture. The developer briefs the primary agent (Claude Code) with an objective and constraints and receives the plan, verdict, and questions back. The primary agent delegates to the Exoma runtime, which handles job, session, and lock, routing, context, and prompt, then sends a bounded task to the secondary agent. The secondary agent reads, searches, and traces the repository and returns candidate evidence; its intended role is read-only, and enforcement varies by provider. The runtime redacts it, checks the contract, shapes a digest with file:line anchors for the primary agent, and reads and writes sessions, facts, evidence, usage, audit, and response artifacts in .workflow/data/ with source anchors and hashes. Evidence candidates are not ground truth." width="900">
+</p>
+
+<sub>The primary agent reasons and writes the code; the developer answers open questions and
+approves implementation. "Read-only" is the secondary agent's role, and how strictly it is
+enforced depends on the provider (see [Security](docs/security.md)). Text version, full verified
+flow, side paths, and storage: [docs/architecture](docs/architecture/README.md).</sub>
+
+Delegated results are treated as **evidence candidates**, not truth. Every delegated call
+returns the same envelope; `digest` appears when the secondary agent's summary parses, and
+`evidence_ref` on the explore/plan/analyze evidence path:
+
+```json
+{ "ok": true, "content": "...", "meta": {}, "digest": {}, "evidence_ref": {} }
+```
+
+The primary agent decides what the evidence means and whether to act on it. A secondary
+agent can be incomplete or wrong even when its output looks plausible.
+
+### Core responsibilities
+
+| Role | Who | Responsibility |
+| --- | --- | --- |
+| **Primary agent** | Claude Code (the integration target) | Reasoning, decisions, code changes, and final review |
+| **Workflow runtime** | The `exoma` package, Python standard library only | Routing, sessions and locks, policy, prompt building, redaction, evidence contracts, digests, persistence, recovery |
+| **Secondary agent** | `opencode`, `codex`, or `agy` | Repository exploration, analysis, planning, and verification evidence |
+
+The design keeps code-writing with the primary agent. The secondary agent's role is
+read-only; the degree to which each provider **enforces** that differs, and the runtime
+states it rather than assuming it. See [Security](docs/security.md).
+
+The principle: let the model do the semantic reasoning, and let deterministic software
+enforce state, contracts, policy, provenance, and execution control.
+
+---
+
+## Relationship to agent-workflow
+
+[agent-workflow](https://github.com/dammar01/agent-workflow) is the implementation and
+research foundation Exoma grew from. It explores separating repository exploration from the
+primary agent's reasoning and implementation context, and how delegation, evidence
+management, and runtime control affect the outcome of the work. That research, including its
+hypotheses and experiments, stays in agent-workflow.
+
+This first release of Exoma repackages that runtime as a library: the same commands,
+contracts and workspace, installed and upgraded like any other Python tool. Exoma is meant to
+grow into a broader library identity, developed from mechanisms that have been tested and
+needs that have been measured.
+
+---
+
+## The name
+
+**Exoma** is a distinctive name for the project. Conceptually, it is inspired by the idea of
+cognitive resources and processes that reach beyond the individual, including discussions of
+*extrasomatic resources* and the *Extended Mind Thesis*.
+
+That inspiration reflects the view that problem solving can be supported by the interplay of
+an AI model, context, tools, memory, and external systems. It does not assume that tools or
+external components literally have minds, nor that an AI becomes smarter simply by using
+more resources.
+
+---
+
+## Vision
+
+Exoma sets out to explore how external systems can help AI agents solve problems more
+effectively: with the right context, a directed investigation, traceable evidence, and a
+compute cost proportionate to its benefit.
+
+Its value is not measured by how many agents it uses or how complex its architecture is, but
+by how far it actually helps an AI solve problems with better quality and conclusions that
+can be accounted for.
+
+**Give agents the context to solve, not the answer to repeat.**
+
+---
+
+## When it is useful
+
+The idea behind the design: on a large codebase, keeping exploration out of the primary
+agent's context should leave it more room to reason. That is a design premise, not a measured
+result; Exoma does not claim a benchmark.
+
+Typical requests (translated, names removed):
+
+| Situation | What was asked | Command |
+| --- | --- | --- |
+| A feature in an unfamiliar area | "Explore the cash-advance input feature: map its files and code, the permissions it uses, and any explicit or special rules." | `explore` |
+| A feature end to end | "Map the project-template feature: a template is created, applied to a project, and then…" | `explore` |
+| A question about a mechanism | "When the audit delta runs, are the commits it checks based on the anchor hash of the last audited commit?" | `analyze` |
+| Reviewing work in progress | "Analyze the changes made in my worktree on this project." | `analyze` |
+| Merging two features | "Make a plan to merge this meetings page with the meetings feature on the Notes page." | `plan` |
+| A cost or speed problem | "Each step uses many tokens and is slow; plan how to lower token use without reducing detection quality." | `plan` |
+| After an implementation | `/.verify`, straight after `/.execute -y` | `verify` |
+| A UI change | "Test it end to end in the browser, several rounds over every category area that changed." | `verify-browser` |
+| Before a commit | `/.sweep` | `sweep` |
+
+It is less attractive when the change is already localized, the relevant file is known, or
+you need an instant answer: a delegated call takes from under a minute to several minutes,
+because the secondary agent actually reads the code. The
+[team guide](docs/team-guide/when-to-use.md) covers choosing per task and how to phrase
+requests.
+
+---
+
+## Quick start
+
+```bash
+uv tool install exoma            # or: pip install exoma
+exoma install                    # dry run: read what it will change in ~/.claude
+exoma install --apply
+```
+
+Then, in a project, run `/.init` in Claude Code (or `exoma init --work-dir .`), and `/.doctor`.
+A project that already has a `.workflow/` from agent-workflow is taken over by `/.upgrade`.
+Details, modes and undo: [installation guide](docs/installation.md).
+
+Ask in natural language; the primary agent routes it:
+
+```text
+you:          where is the authentication logic in this project?
+Claude Code:  [INTENT] explore — location question
+              (runs bash .workflow/run.sh explore '...')
+```
+
+Or call the runtime directly:
+
+```bash
+bash .workflow/run.sh explore 'find the authentication entry point' '<SESSION_ID>'
+```
+
+The generated runner refuses a delegated call without a session id: without one,
+concurrent sessions would share an identifier and overwrite each other's state.
+
+| Command | Type | Purpose |
+| --- | --- | --- |
+| `init` / `upgrade` | local | Enable the runtime in a project / refresh it after the tool is updated |
+| `doctor` | local | Readiness check; writes a report |
+| `sweep` | local | Scan the working tree for changes |
+| `clean` | local | Prune jobs, stale facts, and old sessions |
+| `explore` | delegated | Code map, entry points, ownership |
+| `analyze` | delegated | Causal analysis; no code changes |
+| `plan` | delegated | Evidence-backed implementation steps |
+| `verify` | delegated | Verdict on completed work, with evidence — produced by the secondary agent, not an independent check |
+| `verify-browser` | delegated | Verify a running app in a real browser: the secondary agent drafts the scenario and reviews the evidence; a runtime player drives Playwright |
+| `promote-validate` → `promote-verify` → `promote-write` | local | Turn verified evidence into a Git-tracked knowledge document |
+
+Implementation itself (`/.execute` in Claude Code) is a primary-agent skill, not a delegated
+command; it opens and closes a runtime execution (`plan-record`, `execute-begin`,
+`execute-end`) whose scope a hook enforces for Edit/Write. Asynchronous job commands and the remaining local commands are in the
+[full reference](docs/reference.md#command).
+
+Setup problems and their fixes: [installation guide](docs/installation.md#when-something-is-wrong).
+
+---
+
+## Security
+
+What each secondary-agent provider can read and change: [docs/security.md](docs/security.md).
+
+---
+
+## Documentation
+
+Documentation is layered: the team guide says **how and when**, and the reference says
+**exactly what the runtime does** — see [docs/](docs/README.md).
+
+| Document | Contents |
+| --- | --- |
+| [docs/installation.md](docs/installation.md) | Requirements, install, per-project setup, updating, uninstalling |
+| [docs/security.md](docs/security.md) | What each secondary-agent provider is allowed to read and change |
+| [docs/team-guide](docs/team-guide/README.md) | For developers: getting started, when to use it, task framing, examples, troubleshooting |
+| [docs/architecture](docs/architecture/README.md) | Verified request flow, components, and storage |
+| [docs/reference.md](docs/reference.md) | Complete technical reference: configuration, jobs, fact store, evidence reuse, verify modes, sessions, tests, CI |
+| [docs/runtime-contracts.md](docs/runtime-contracts.md) | Which `.workflow/config.json` keys the runtime obeys, and which it cannot enforce |
+| [docs/limitations.md](docs/limitations.md) | Known limitations |
+| [docs/evaluation/metrics.md](docs/evaluation/metrics.md) | How every figure `exoma report` prints is computed |
+| [CHANGELOG.md](CHANGELOG.md) / [RELEASE.md](RELEASE.md) | Release history and procedure |
+
+[ci.yml](.github/workflows/ci.yml) runs the version stamp, manifest, stdlib-only gate, and
+test suites, plus a clean install of the built wheel, on every push on Linux and Windows,
+spending no provider quota; [publish.yml](.github/workflows/publish.yml) publishes a release
+tag to PyPI; [e2e-full.yml](.github/workflows/e2e-full.yml) is manual because it calls a real
+secondary agent.
+
+---
+
+## Limitations
+
+Exoma adds an execution layer, and with it additional latency, additional provider calls
+and compute, new failure modes, provider-specific security limits, and maintenance
+complexity. It is not preferable for every task. Full list: [docs/limitations.md](docs/limitations.md).
+
+## License
+
+Apache License 2.0 — see [LICENSE](LICENSE) for the authoritative text.
+
+Use, modification, and distribution are permitted, including commercially, provided the
+copyright notice and licence are retained and modified files are marked as changed. The
+licence includes an express patent grant that terminates for any party initiating patent
+litigation over the work. The software is provided without warranty of any kind. This
+summary is not legal advice.
+
+```text
+Copyright 2026 dammar01
+```