Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
349795b
fix(security): claim a bus task only when a worker is free (LSR-075)
homer6 Nov 14, 2026
a39221d
docs: add a security policy (SECURITY.md)
homer6 Nov 15, 2026
a1f7d76
fix(build): pin the base images by digest
homer6 Nov 15, 2026
4517b50
chore(license): MIT license, SPDX headers, third-party notices and co…
homer6 Nov 15, 2026
8a981bf
chore(license): name the copyright holder OramaSearch, Inc.
homer6 Nov 15, 2026
6c621aa
build: commit an SBOM (sbom.spdx.json) and the script that makes it
homer6 Nov 15, 2026
1c227ca
docs(license): contributions under a copyright-assignment CLA instead…
homer6 Nov 16, 2026
db0e159
build: regenerate the SBOM
homer6 Nov 16, 2026
6dae594
Merge pull request #72 from oramasearch/docs/security-policy
homer6 Nov 16, 2026
67c2623
Merge pull request #73 from oramasearch/fix/1003-pin-base-images
homer6 Nov 16, 2026
fab20b1
Merge pull request #70 from oramasearch/fix/lsr-075-bus-backpressure
homer6 Nov 16, 2026
389ca4a
Merge pull request #76 from oramasearch/chore/g4-licenses
homer6 Nov 16, 2026
9590770
fix(security): bound the conversation memory and key bus turns by Lak…
homer6 Nov 14, 2026
f132eda
chore(license): SPDX headers on files added since the licence pass
homer6 Nov 16, 2026
8b067cd
build: regenerate the SBOM
homer6 Nov 16, 2026
e5a1c7f
Merge pull request #71 from oramasearch/fix/lsr-076-bounded-history
homer6 Nov 16, 2026
39cf4dc
docs: prepare the tree for the public export (G3)
homer6 Nov 15, 2026
b28f68c
docs: agent files ship with the public repo
homer6 Nov 15, 2026
1ceec3c
build: regenerate the SBOM
homer6 Nov 16, 2026
c9cc363
Merge pull request #75 from oramasearch/docs/g3-public-cleanup
homer6 Nov 16, 2026
7a3a416
docs(release): v0.3.0 notes and version
homer6 Nov 16, 2026
610cc74
chore(sbom): regenerate for v0.3.0
homer6 Nov 16, 2026
ed44e90
Merge pull request #79 from oramasearch/release/v0.3.0
homer6 Nov 16, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,14 @@
# AGENTS.md: working in agent-application

The ApplicationAgent: builds web apps and data apps from a description, commits them to a lake repository, and deploys them as lake Apps after the person confirms. Built on agent-runtime. Epic: oramasearch/lake#297.
The ApplicationAgent: builds web apps and data apps from a description, commits them to a Lake repository, and deploys them as Lake Apps after the person confirms. Built on agent-runtime. Read `README.md` and `docs/README.md` first.

## Non-negotiables (org-wide)
- **No AI attribution** anywhere: no Co-Authored-By, no "Generated with", no mention of AI in commits, PRs, tags or release notes.
## Build and test
- Python with uv, never pip: `uv sync`, then `uv run --group dev pytest`.

## Non-negotiables
- **No AI attribution** anywhere: no AI Co-Authored-By trailer, no "Generated with", no mention of AI in commits, PRs, tags or release notes.
- **No time or size estimates.** Do the work; report concrete results.
- **Docs in the same change:** update README.md (and any docs page) with every code change.
- **Feature branch + PR.** Never push to `main`. PRs reference their issue with `Refs #N`, never an auto-close keyword.
- **Private by default.** This repo and its Docker Hub image `oramasearch/agent-application` are private; never make either public.
- **Feature branch + PR**, Conventional Commits. Never push to the default branch. PRs reference their issue with `Refs #N`, never an auto-close keyword.
- Never run a formatter over files you did not otherwise change.
- Never write the word "seam": name the mechanism (interface, extension point, boundary).
82 changes: 82 additions & 0 deletions CLA.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
# Contributor License Agreement (copyright assignment)

Thank you for contributing to a project of OramaSearch, Inc. This agreement says what happens to
the rights in what you contribute. It applies to every Contribution you Submit to any project owned
by OramaSearch, Inc., now or later. Please read it before you sign; you sign it once.

## 1. Definitions

- **"We"** and **"Us"** mean OramaSearch, Inc.
- **"You"** means the individual who signs this agreement. If you contribute on behalf of your
employer or another organization, see section 8.
- **"Contribution"** means any work of authorship (code, documentation, tests, designs, data or
anything else) that You Submit to a project We own, including any changes to it that You Submit
later.
- **"Submit"** means sending a Contribution to Us or to a project We own in any form: a pull request,
a patch, an issue, a comment, or any other channel We use to receive changes.
- **"Project"** means the software or other material, owned by Us, to which You Submit a
Contribution.

## 2. Assignment of copyright

You assign to Us, with effect from the moment You Submit each Contribution, all right, title and
interest worldwide in the copyright in that Contribution, including all renewals and extensions.

To the extent the law allows, You waive, and agree not to assert against Us, Our licensees or Our
successors, any moral rights You have in the Contribution.

## 3. If the assignment is not effective

If, under the law that applies, the assignment in section 2 is not effective for any part of a
Contribution, You grant Us instead an exclusive, perpetual, worldwide, irrevocable, royalty-free,
transferable licence, with the right to grant sublicences through multiple tiers, to use, copy,
modify, distribute, make available, publicly perform and display that part, and to license it to
others under any terms.

## 4. Licence back to You

We grant You a perpetual, worldwide, non-exclusive, royalty-free, irrevocable licence to use, copy,
modify and distribute Your own Contribution for any purpose. This licence does not cover the rest
of the Project, which You receive under the Project's own licence.

## 5. Patent licence

You grant Us, and everyone who receives the Project from Us or through Us, a perpetual, worldwide,
non-exclusive, royalty-free, irrevocable patent licence to make, have made, use, sell, offer for
sale, import and otherwise transfer the Contribution, alone or combined with the Project, under
every patent claim You can license that the Contribution infringes, alone or in that combination.

## 6. How We may license the Project

We may license the Project, and the Contributions in it, under any terms, including the MIT
License under which the Project is published today. We are not obliged to use Your Contribution.

## 7. What You confirm

You confirm that:

- each Contribution is Your original work, or You have the right to Submit it under this agreement;
- if any part of a Contribution is someone else's work, You say so when You Submit it, with where it
came from and its licence, and that part is not covered by sections 2 and 3;
- You are legally able to enter into this agreement;
- if Your employer has rights in what You create, You have its permission to Submit the
Contribution under this agreement, or the employer has signed the entity agreement (section 8).

You will tell Us if any of this stops being true.

## 8. Contributions on behalf of an organization

If You contribute as part of Your work for an employer or another organization, that organization
must agree as well. Write to **opensource@orama.com** for the entity version of this agreement.

## 9. No warranty

Except as section 7 says, You provide each Contribution "as is", without warranties or conditions
of any kind, express or implied.

## 10. How You sign

When You open Your first pull request to a project We own, a bot comments on it with a link to this
agreement. Signing there, with Your GitHub account, is Your electronic signature of this agreement,
and covers every Contribution You Submit afterwards. A pull request from someone who has not signed
is not merged.
84 changes: 84 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@

# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at **conduct@orama.com**. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of actions.

**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations
77 changes: 77 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
# Contributing to agent-application

Thank you for helping. This document says how to build and test agent-application, how a change gets in,
and the one thing every contributor does first: sign the Contributor License
Agreement.

## Before you start

- For a bug, open an issue with what you did, what you expected and what happened, and the
version or commit.
- For a larger change (a new feature, a new dependency, a change to an interface), open an issue
first so the approach can be agreed before you write it.
- **Security issues are never reported in a public issue.** See [SECURITY.md](SECURITY.md): write
to **security@orama.com**.

## Build and test

You need Python 3.12 or later and [uv](https://docs.astral.sh/uv/).

```sh
uv sync # creates .venv with the locked dependencies, including the test tools
uv run pytest # the whole test suite
```

The evaluation suite runs with `uv run application-agent-evals`.

The container image is built from the `Dockerfile`:

```sh
docker build -t agent-application:local .
```

## Making a change

1. Fork the repository and branch from `dev`. `main` is the last release; it moves only when a
release is cut.
2. Keep one change per pull request, with the tests that prove it. A change in behavior updates
the documentation it touches in the same pull request.
3. Write commit messages in the [Conventional Commits](https://www.conventionalcommits.org/) form,
for example `fix(api): reject an empty name`.
4. Sign the Contributor License Agreement before your first pull request is merged (next section).
5. Open the pull request against `dev`. Start its description with what changes, why, and how.

A maintainer reviews it. Pull requests are merged with a merge commit, so every commit you make
stays in the history.

## Contributor License Agreement

agent-application is owned by OramaSearch, Inc. Every contributor signs the
[Contributor License Agreement](CLA.md) (CLA) once, before their first pull request is merged. Under
it you assign the copyright in your contributions to OramaSearch, Inc., you keep a licence to use
your own contributions for any purpose, and you grant a patent licence for them. The project is
published under the MIT License (see [LICENSE](LICENSE)).

When you open your first pull request, a bot comments on it with a link to the agreement. Sign
there with your GitHub account; it covers all your later contributions to projects of OramaSearch,
Inc. If you contribute as part of your job, your employer signs too: write to
**opensource@orama.com** for the entity agreement.

## License headers

Every source file starts with the line `SPDX-License-Identifier: MIT`, in that file's comment
syntax, for example `// SPDX-License-Identifier: MIT`. Add it to a new file yourself, or run:

```sh
python3 tools/spdx-headers.py # adds the line where it is missing
python3 tools/spdx-headers.py --check # lists files without it
```

Code copied from another project keeps its own license header and is listed in
[THIRD_PARTY_LICENSES](THIRD_PARTY_LICENSES). Say so in the pull request, with where it came from
and its license; it must be compatible with the MIT License.

## Code of conduct

Everyone taking part follows the [Code of Conduct](CODE_OF_CONDUCT.md). Report unacceptable
behavior to **conduct@orama.com**.
11 changes: 11 additions & 0 deletions COPYRIGHT
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
Copyright (c) 2026 OramaSearch, Inc.

This project is licensed under the MIT License; the full text is in LICENSE.
Every source file Orama wrote carries the tag `SPDX-License-Identifier: MIT`,
added and kept current by tools/spdx-headers.py.

Components written by others keep their own licenses. They are listed, with
their license texts, in THIRD_PARTY_LICENSES.

Contributions are accepted under the Contributor License Agreement in CLA.md,
which assigns their copyright to OramaSearch, Inc.; see CONTRIBUTING.md.
10 changes: 9 additions & 1 deletion Dockerfile
Original file line number Diff line number Diff line change
@@ -1,13 +1,21 @@
# syntax=docker/dockerfile:1
# SPDX-License-Identifier: MIT

# ApplicationAgent is private on Docker Hub as oramasearch/agent-application.
# Bases are pinned by their multi-platform index digest (lake#1003); a new base is a reviewed
# change of the digest, not a moved tag.
FROM python:3.12-slim@sha256:5e2bdb1b0d542d5039cffb8181c65930093949194a65c365dfb1b0fe13a4fa5b AS build
COPY --from=ghcr.io/astral-sh/uv:0.11.7@sha256:240fb85ab0f263ef12f492d8476aa3a2e4e1e333f7d67fbdd923d00a506a516a /uv /usr/local/bin/uv

# ApplicationAgent, published on Docker Hub as oramasearch/agent-application.
FROM python:3.12-slim AS build
COPY --from=ghcr.io/astral-sh/uv:0.11.7 /uv /usr/local/bin/uv
WORKDIR /app
COPY pyproject.toml uv.lock README.md ./
COPY src ./src
RUN uv sync --frozen --no-dev --no-editable

FROM python:3.12-slim
FROM python:3.12-slim@sha256:5e2bdb1b0d542d5039cffb8181c65930093949194a65c365dfb1b0fe13a4fa5b
RUN useradd --uid 10001 --create-home agent
WORKDIR /home/agent
COPY --from=build /app/.venv /app/.venv
Expand Down
21 changes: 21 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2026 OramaSearch, Inc.

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.
Loading