loreli 0.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Arnout Kazemier
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,103 @@
+# Loreli
+
+Loreli is an agentic system that uses the GitHub patterns we're familiar with for orchestration. Issues becomes actions for agents. Pull Requests are review tasks. Discussions are where plans are discussed and then raised as issues on approval. The system uses an antagonist style where OpenAI will always be checked by Antrophic, ensuring you get input from both models.
+
+## Status
+
+Active development. Expect breaking changes until the first stable release.
+
+## Goals
+
+- Use GitHub issues as the system's action queue
+- Use pull requests as review tasks with explicit acceptance criteria
+- Use discussions as planning and approval forums
+- Maintain an antagonist style: every decision is checked by an opposing model
+- Provide an MCP server to expose orchestration primitives to agents and tools
+
+### Architecture Overview
+
+- GitHub Repo (source of truth)
+  - Issues: actionable work items, one per task
+  - Discussions: planning, debates, and approval
+  - Pull Requests: review and acceptance gates
+- MCP Server (orchestrator)
+  - Watches GitHub events (issues, PRs, discussions)
+  - Assigns tasks to agent runners
+  - Stores run state and artifacts
+- Agent Runners
+  - Worker processes that perform tasks (coding, analysis, documentation)
+  - Must use the MCP server for all GitHub interactions
+- Antagonist Pairing
+  - For every primary agent action, a secondary agent provides critique
+  - MCP server aggregates both and posts back to GitHub
+
+### Workflow (Happy Path)
+
+1. Planning happens in a GitHub Discussion.
+2. When a plan is approved, each action item becomes an Issue.
+3. The MCP server detects new issues and assigns them to agents.
+4. The primary agent produces a proposal; the antagonist critiques it.
+5. The MCP server posts both to the Issue and optionally creates a PR.
+6. The PR is the review task; it links to the Issue and Discussion.
+7. Reviewers approve or request changes; MCP server updates status.
+
+### Core Components
+
+#### MCP Server
+
+Responsibilities:
+- Subscribe to GitHub webhooks
+- Maintain a task queue keyed by Issue/PR IDs
+- Provide MCP methods for:
+  - `list_issues`, `get_issue`, `comment_issue`
+  - `create_pr`, `update_pr`, `request_review`
+  - `list_discussions`, `create_discussion`, `comment_discussion`
+  - `assign_agent`, `store_artifact`, `fetch_artifact`
+- Enforce antagonist pairing
+
+#### Issue Model
+
+Each Issue should have:
+- Title: actionable, specific
+- Labels: `type/*`, `priority/*`, `status/*`
+- Checklist: acceptance criteria
+- Links: relevant Discussion and related PR
+
+#### PR Model
+
+Each PR should:
+- Reference the Issue it resolves
+- Include a summary, risks, and test plan
+- Include a section for antagonist critique
+
+### Antagonist Style
+
+Every action must be checked by an opposing model:
+- Primary agent: propose solution and implementation
+- Antagonist agent: identify risks, missing tests, alternative approaches
+- MCP server posts both as a paired response
+- Issues and PRs are not marked complete without antagonist feedback
+
+### Data and State
+
+- GitHub is the canonical record of decisions and status
+- MCP server stores ephemeral state (task queue, agent assignments)
+- Artifacts (logs, intermediate outputs) stored in a simple object store
+
+### Security and Access
+
+- MCP server uses GitHub App authentication
+- Principle of least privilege: read/write issues, PRs, discussions only
+- All agent actions are logged and attributed in GitHub
+
+### Initial Milestones
+
+1. MCP server skeleton with GitHub webhook handling
+2. Basic issue-to-agent assignment
+3. Antagonist pairing and GitHub comments
+4. PR creation and review loop
+5. Stable operational docs and onboarding
+
+## License
+
+MIT

package/index.js

@@ -0,0 +1,8 @@
+export function placeholder() {
+  return {
+    status: "placeholder",
+    message: "Loreli is under active development. This package reserves the name.",
+  };
+}
+
+export default placeholder;

package/package.json

@@ -0,0 +1,23 @@
+{
+  "name": "loreli",
+  "version": "0.0.0",
+  "description": "Loreli is an agentic system that uses the GitHub patterns we're familiar with for orchestration. Issues becomes actions for agents. Pull Requests are review tasks. Discussions are where plans are discussed and then raised as issues on approval. The system uses an antagonist style where OpenAI will always be checked by Antrophic, ensuring you get input from both models.",
+  "keywords": [
+    "loreli",
+    "github",
+    "agentic",
+    "system",
+    "orchestration"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "github.com/3rd-Eden/loreli"
+  },
+  "license": "MIT",
+  "author": "Arnout Kazemier",
+  "type": "module",
+  "main": "index.js",
+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1"
+  }
+}