agora-framework 0.3.1__tar.gz

agora_framework-0.3.1/.gitignore

@@ -0,0 +1,12 @@
+.venv/
+node_modules/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+__pycache__/
+*.py[cod]
+.agora/
+.agents/skills/agora-*/
+.claude/commands/agora.*.md

agora_framework-0.3.1/AGENTS.md

@@ -0,0 +1,71 @@
+# Instructions for coding agents
+
+- Preserve Agora's programming-language, LLM-provider, model, and development-process independence.
+- Do not introduce LLM SDKs or provider dependencies into the core CLI.
+- Implement Agora scripts and automation in Python, not JavaScript or TypeScript.
+- Keep the protocol Markdown-first, human-readable, and portable across agent environments.
+- Add tests for domain rules and their failure paths.
+- Update templates and documentation whenever the installed protocol changes.
+- Treat filesystem and Git as the persistent collaboration substrate.
+- Use Conventional Commits 1.0.0 for every commit: `<type>[optional scope][!]: <description>` with
+  bodies and footers separated by a blank line.
+- Keep environment-specific output in integration adapters.
+- Keep actor private keys outside Agora; persist only public identity and signed verification
+  evidence, preserve rotation and revocation history, and bind authorizations to exact durable
+  operations and materialized session context before execution.
+- Route authenticated lifecycle mutations through prepared `ACTION.md` intents, bind signatures to
+  their work preconditions, and reapply all Method Pack rules immediately before mutation.
+- Keep Tool Pack commands structured, shell-free, and free of credential inputs.
+- Give Tool Packs bounded direct-process timeouts and captured-output limits; describe external
+  containers or runners as the isolation boundary for filesystem, network, syscalls, and resources.
+- Keep ecosystem Tool Pack capabilities provider-neutral; place Jira, CI/CD, documentation, and
+  cloud translation in reviewed external adapters rather than the kernel.
+- Keep GitLab merge-request adapters on an exact native subset; do not discard review-decision bodies
+  or reinterpret conditional list and merge flags as neutral semantics.
+- Keep GitHub ecosystem adapters behind provider-neutral contracts; keep ruleset administration
+  read-only until a neutral policy artifact is validated, and keep release publication ungranted.
+- Redact GitHub secret scanning values before provider output becomes durable; never request secret
+  locations or raw credentials merely to build a synchronization snapshot.
+- Keep Tool Sync provider-neutral, explicit, read-only, bounded, and persisted as an ordinary Tool
+  Run; never add background reconciliation or allow write risk through the sync path.
+- Prefer a reviewed native provider CLI when it is installed and non-interactive; use a team wrapper
+  for normalization and MCP only as an explicit alternative transport.
+- Give reviewed CLI adapters a structured local version command and a tested minimum version; never
+  infer compatibility from executable presence alone when launching governed work.
+- Use an explicit conforming operation subset when a provider CLI cannot implement a full neutral
+  contract; never invent generic plan, apply, or destructive semantics.
+- Never map GitLab issue creation to the neutral work-management contract unless the adapter can
+  preserve its required work-item type; restrict dynamic lifecycle subcommands to close or reopen.
+- Keep CI cancellation and deployment capabilities opt-in; combine production authority with
+  explicit Method Pack policy, evidence, and operation approval requirements.
+- Keep GitLab CI/CD adapters on an exact native subset; do not discard the neutral pipeline identity
+  when translating triggers or expose deployment operations without immutable artifact binding.
+- Keep documentation publication and archival opt-in; treat remote pages as external state and
+  persist their identifiers as Agora artifacts or evidence when lifecycle gates require them.
+- Keep Confluence updates bound to native optimistic-concurrency tokens; expose only an explicit
+  adapter subset when space-scoped search cannot be translated without provider-aware escaping.
+- Keep cloud apply and destruction opt-in; require reviewed immutable plans, external workload
+  identity, explicit approvals, and durable evidence appropriate to the target environment.
+- Keep incident resolution opt-in and distinct from recovery evidence; bound observability queries
+  and redact sensitive provider output before it becomes durable.
+- Keep registry indexes and snapshots Markdown-first; verify remote releases before extraction,
+  validate every contained pack before copying, persist provenance, and preserve
+  project-over-user-over-bundled precedence.
+- Keep registry trust public-only and Markdown-first; preserve project-over-user key precedence and
+  never allow explicit key input to bypass a persisted revocation.
+- Keep registry updates preview-first, forward-only, authenticated, transactional, and historically
+  auditable; never refresh installed packs implicitly.
+- Keep pack dependencies versioned, cross-kind, scope-local, cycle-free, and resolved before writes;
+  never replace a dependency when that would break an installed consumer.
+- Keep catalog pack provenance installer-owned and checksum-pinned; keep pack updates preview-first,
+  forward-only, composition-safe, and protective of local amendments.
+- Keep pack update histories continuous and pack composition locks deterministic; refresh locks only
+  after successful managed mutations or an explicit reviewed lock command.
+- Keep pack removal preview-first and rollback-protected; block reverse dependents and durable
+  references, require explicit unused-dependency pruning, and preserve a scope-level audit record.
+- Treat Scrum and Kanban as bundled examples, never as privileged core workflows.
+- Preserve recursive swarm cycle checks and configured delegation depth.
+- Preserve explicit child-work acceptance and reference-based result collection across swarms.
+- Keep usage accounting provider-neutral, append-only, evidence-backed, and bounded by inherited
+  work budgets; external runtimes measure consumption and Agora validates submitted amounts.
+- Prefer small, reviewable changes and abstractions backed by a concrete lifecycle requirement.

agora_framework-0.3.1/CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# Contributing to Agora
+
+Agora is experimental. Prefer small changes that remain inspectable after installation.
+
+The complete verification command is:
+
+```bash
+uv run python scripts/verify_all.py
+```
+
+Run individual checks while iterating:
+
+```bash
+uv sync --extra dev
+uv run ruff format --check .
+uv run ruff check .
+uv run pytest
+uv run python scripts/check_docs.py
+uv build
+uv run python samples/basic-swarm/run.py
+uv run python samples/llm-environments/run.py
+uv run python samples/custom-lifecycle/run.py
+uv run python samples/tool-integration/run.py
+uv run python samples/handoffs/run.py
+uv run python samples/recursive-swarms/run.py
+uv run python samples/delegated-work/run.py
+uv run python samples/operational-query/run.py
+uv run python samples/operational-loop/run.py
+uv run python samples/interruptions/run.py
+uv run python samples/project-upgrade/run.py
+uv run python samples/concurrent-writes/run.py
+uv run python samples/pack-registry/run.py
+uv run python samples/remote-registry/run.py
+uv run python samples/github-end-to-end/run.py
+```
+
+## Rules
+
+- Preserve programming-language, runtime, provider, model, development-process, agent, IDE, and
+  cloud independence.
+- Implement Agora automation in Python; do not introduce JavaScript or TypeScript tooling.
+- Do not add an LLM SDK to the core CLI.
+- Keep operational state in Markdown and Git, not a parallel database or JSON snapshot.
+- Keep adapter-specific output outside Method Packs and domain rules.
+- Prefer reviewed native CLI adapters when a provider CLI already exists; keep MCP optional and
+  explicit rather than an automatic fallback.
+- Declare and validate a partial adapter when the native CLI implements only a safe subset of a
+  provider-neutral contract.
+- Keep Tool Pack commands structured and provider credentials outside durable inputs.
+- Keep Method Pack identifiers open; bundled packs are examples, not core enums.
+- Add tests for capabilities, role actions, transitions, WIP, gates, approvals, handoffs,
+  interruptions, recursive swarms, delegated work, sessions, tool runs, queries, validation, and
+  filesystem behavior.
+- Update templates and documentation whenever the installed protocol changes.
+- Keep explanatory material under `docs/`, operational protocol sources under `templates/`, and
+  plugin-owned run output under its existing plugin directory.
+- Use Mermaid when a decision tree, lifecycle, sequence, scope hierarchy, or ownership boundary is
+  easier to understand visually. Keep adjacent prose and commands authoritative, and prefer a table
+  when relationships are static rather than sequential.
+- Keep `scripts/verify_all.py` aligned with every executable sample and distribution check.
+- Never persist raw credentials; store only external authentication references.
+- Never persist registry private signing keys; trust records contain public keys only.
+- Treat humans, AI agents, services, automations, and swarms as compatible actor forms governed by
+  role contracts.
+- Use Conventional Commits 1.0.0 for every commit. Use `feat` for features, `fix` for fixes, and `!`
+  or a `BREAKING CHANGE:` footer for breaking changes.
+
+## Commit messages
+
+```text
+<type>[optional scope][!]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+Examples:
+
+```text
+feat(governance): validate repository commit messages
+fix(upgrade): preserve customized tool operations
+docs: explain local writer locks
+feat(protocol)!: require explicit release evidence
+```
+
+Agora projects materialize this rule in `.agora/STANDARDS.md`. When exercising Agora itself, prefer
+the governed `repository/commit` Tool Pack operation so the input is validated before Git runs.
+
+Generated distributions, virtual environments, local `.agora`, and installed agent commands are not
+committed to this repository.

agora_framework-0.3.1/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 2026 Agora contributors
+
+   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.