@atolis-hq/wake 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

package/README.md

@@ -0,0 +1,140 @@
+# Wake
+
+Wake is a local autonomous agent control plane for software development. It
+watches the work channels your team already uses, such as GitHub Issues,
+decides each item's next lifecycle step with deterministic rules, and launches
+local coding-agent CLIs only when agentic execution is actually needed.
+
+Wake is the control plane and decision-maker. It launches and manages local
+agent sessions for each unit of agentic work.
+
+## The Problem
+
+Modern coding agents are powerful, but sustained development work still needs a
+lot of manual orchestration. Agents are usually started by hand, tied to one CLI
+surface, and optimized for interactive sessions instead of managed execution
+over time.
+
+That leaves hard operational gaps: deciding what should happen next, choosing
+the right tool and model for each step, preserving state across interruptions,
+running deterministic housekeeping outside the LLM path, and letting a human
+resume the exact local session when direct intervention is fastest.
+
+Wake exists to close that gap. It wraps existing agent CLIs in a local control
+plane that can apply scripted routing rules, move work through explicit
+lifecycle steps, resume or hand off sessions, and keep deterministic processes
+out of the token-burning path wherever possible.
+
+## Vision
+
+Wake should make reliable, resumable, token-aware local agent execution
+practical. The default operating model is asynchronous and channel-driven: work
+enters and progresses through durable external systems, while execution happens
+locally in an inspectable workspace or sandbox.
+
+Wake is not trying to replace coding agents, issue trackers, or source control.
+It coordinates across them. Over time it should become the layer that picks
+work, decides the next step, invokes the right local tool or deterministic
+process, persists state, and resumes later without losing context.
+
+For more detail, see [docs/vision.md](docs/vision.md) and
+[docs/architecture.md](docs/architecture.md).
+
+## Feature Overview
+
+- **Wake decides, the agent runs.** Choosing the CLI, model, and lifecycle
+  transition is a control-plane decision; agents do the work and report an
+  outcome.
+- **Issue-driven by default.** Wake currently integrates with GitHub Issues and
+  reports questions, approvals, progress, and results back through the ticket.
+- **Explicit lifecycle stages.** Work can move through configurable stages such
+  as refinement and implementation instead of disappearing into one opaque
+  session.
+- **Event-sourced and restart-safe.** The durable record is an append-only event
+  log; projections can be rebuilt, and the loop can crash and resume without
+  losing its place.
+- **Local and inspectable.** Config, events, state, runs, workspaces, and prompts
+  live in a plain-file Wake home directory.
+- **Sandbox-oriented execution.** Wake can run from a persistent Docker sandbox
+  with durable auth state and mounted Wake home data.
+- **Runner agnostic.** Claude Code, Codex, Cursor, and fake runners sit behind
+  runner adapters so Wake owns policy and routing rather than depending on one
+  provider.
+- **Human resumption.** A human can pick up the exact local agent session when a
+  direct terminal intervention is the best way forward.
+- **Operator correlation escape hatch.** `wake correlate <workItemKey>
+  <resourceUri>` lets an operator hand-declare that a resource (a PR, a Slack
+  thread, etc.) belongs to an existing work item when nothing detected the
+  link automatically. See [docs/configuration.md](docs/configuration.md).
+
+Current runner capability differences are documented in
+[docs/runner-comparison.md](docs/runner-comparison.md).
+
+## Getting Started
+
+Wake is distributed as the `@atolis-hq/wake` npm package. You can run the CLI
+with `npx` or install it globally:
+
+```sh
+npx @atolis-hq/wake init ./wake-home
+```
+
+```sh
+npm install -g @atolis-hq/wake
+wake init ./wake-home
+```
+
+`wake init` creates a Wake home directory with `config.json`, prompt templates,
+Docker sandbox assets, runtime directories, and shell launchers:
+
+- `wake.sh` for bash, Git Bash, WSL, and similar shells.
+- `wake.ps1` for PowerShell.
+
+Use the generated launcher from the Wake home for day-to-day operation. The
+launcher runs host setup commands locally and forwards runtime commands into the
+sandbox with the correct Wake home mounted at `/wake`.
+
+```sh
+cd ./wake-home
+./wake.sh sandbox build
+./wake.sh sandbox up
+./wake.sh sandbox setup
+./wake.sh tick
+./wake.sh start
+```
+
+The default sandbox image includes Node, Git, GitHub CLI, Claude Code, Codex,
+Cursor, and the Wake runtime. Treat the generated `docker/Dockerfile` as a
+starting point for your own environment: add the tools your repositories need,
+then rebuild with `./wake.sh sandbox build`. Wake writes the package location to
+`config.json` as `dev.repoRoot` so sandbox rebuilds use the same bundled assets;
+editing your generated Dockerfile or prompts is expected and future package
+upgrades should not overwrite that Wake home.
+
+Common commands:
+
+```sh
+./wake.sh ui
+./wake.sh tick
+./wake.sh start
+./wake.sh stop
+./wake.sh sandbox resume <session-id> --cwd "/wake/workspaces/<workId>"
+```
+
+For a source checkout development workflow, use:
+
+- [docs/development.md](docs/development.md)
+
+Recommended local practices:
+
+- Use a separate git identity for Wake-managed agent work so automated commits
+  and human commits are easy to distinguish.
+- Prefer the prebuilt sandbox flow when running real agent work locally.
+- Treat the default Dockerfile as a starting point. It includes common tooling
+  such as Node, but it is expected to be edited for the repositories and agents
+  you want Wake to operate on.
+
+## Development
+
+Local setup, commands, sandbox operation, auth setup, UI notes, and GitHub
+polling details are documented in [docs/development.md](docs/development.md).