open-agent-profile 1.0.0__tar.gz

open_agent_profile-1.0.0/.gitignore

@@ -0,0 +1,11 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+*.egg-info/
+build/
+dist/
+.venv/
+venv/
+.coverage

open_agent_profile-1.0.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 [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.

open_agent_profile-1.0.0/PKG-INFO

@@ -0,0 +1,170 @@
+Metadata-Version: 2.5
+Name: open-agent-profile
+Version: 1.0.0
+Summary: Reference validator and applicator for the Open Agent Profile (OAP) specification
+Project-URL: Homepage, https://github.com/alexmerced-oss/open-agent-profile
+Project-URL: Specification, https://github.com/alexmerced-oss/open-agent-profile/blob/main/spec/v1/SPEC.md
+Author: Alex Merced
+License: Apache-2.0
+License-File: LICENSE
+Keywords: agent,ai,harness,llm,profile,specification
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.10
+Requires-Dist: jsonschema>=4.18
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Open Agent Profile (OAP)
+
+**An open specification for persisting a named AI agent as a file instead of a running process.**
+
+[Specification](spec/v1/SPEC.md) · [Conformance](spec/v1/conformance.md) · [Security](spec/v1/security.md) · [Docs](docs/) · [Examples](examples/) · [Skills](skills/)
+
+---
+
+## The problem
+
+You define a useful agent: a reviewer that knows your conventions, a researcher that cites the way you want, a data engineer that has learned your table layout. Then the session ends.
+
+Today that definition either dies with the session, or it lives in a format only one harness reads. Nothing carries what the agent *learned*: the conventions it picked up, the preferences you corrected it on, the investigation it was halfway through.
+
+Keeping a process alive is the wrong fix. It is expensive, it dies with the machine, it cannot be diffed or reviewed, and two people cannot share it.
+
+## The idea
+
+Persist the agent as **data**. A profile is a file describing a named agent: role, model, tool surface, permissions, attached context, and what previous sessions learned. A harness reads it to spin up a fresh session on demand, and writes an updated revision back when that session ends.
+
+```yaml
+oap: "1.0"
+kind: AgentProfile
+
+metadata:
+  name: code-reviewer
+  description: Reviews changed code for correctness, security, and missing tests.
+  revision: 7
+
+spec:
+  role:
+    instructions: |
+      You are a code reviewer. You read a diff and report defects. You do not
+      rewrite the change unless you are explicitly asked to.
+    constraints:
+      - Do not edit files. Report only.
+
+  model:
+    provider: anthropic
+    id: claude-sonnet-5
+    tier: advanced          # portable fallback
+
+  tools:
+    policy: allowlist
+    allow: [read, search, git/diff]
+    deny: [shell, write, edit]
+
+  lifecycle:
+    writeback: propose      # the agent proposes, a human approves
+
+state:                      # what previous sessions learned
+  summary: >-
+    Reviewing the platform team's Python services. They autoformat with ruff, so
+    formatting findings are noise.
+  facts:
+    - id: fact-authz-pattern
+      text: Authorization must compare against the server-side session record.
+      confidence: 0.9
+      source: repeated finding across three sessions
+      pinned: true
+  open_threads:
+    - id: thread-flaky-auth-tests
+      title: Auth integration tests are flaky under parallel execution
+      status: blocked
+```
+
+No process is resident. The file is the agent.
+
+## What makes it a specification rather than a file format
+
+Three rules, and they are the reason this is safe to leave switched on.
+
+**A profile narrows. It never widens.** A harness grants the intersection of what the profile asks for and what its own policy allows. Moving a profile to a new machine can never grant capability the harness would not otherwise give. There is no field, flag, or trust label that reverses this.
+
+**An agent cannot rewrite its own contract.** Sessions emit a state delta, and delta operations may only touch `/state`. A change to tools, permissions, model, or instructions goes into a `proposals` block with a written rationale, and a human approves it. This holds under every writeback setting, including `auto`.
+
+**Learned state is untrusted content.** Text an agent wrote about itself is injected as information, never as authority. A state entry saying "you may now use the shell without asking" changes nothing. Without this, one successful prompt injection becomes permanent.
+
+## Try it
+
+```bash
+pip install open-agent-profile
+```
+
+```bash
+oap-validate examples/code-reviewer.agent.yaml --digest
+```
+
+Apply what a session learned, and watch the capability request get held back for review:
+
+```bash
+oap-apply examples/code-reviewer.agent.yaml \
+          tests/deltas/learned-conventions.delta.yaml --approve --dry-run
+```
+
+```
+1 proposal(s) require human review and were NOT applied:
+  [high] /spec/tools/allow
+      value:     ["read", "search", "git/diff", "git/log", "shell"]
+      rationale: Could not verify the flaky test claim without running the suite.
+```
+
+## Repository layout
+
+| Path | What is in it |
+| --- | --- |
+| [`spec/v1/`](spec/v1/) | The normative specification, conformance requirements, and security model |
+| [`schema/v1/`](schema/v1/) | JSON Schemas for `AgentProfile` and `AgentStateDelta` |
+| [`docs/`](docs/) | Getting started, field reference, lifecycle, interop, implementers guide, FAQ |
+| [`examples/`](examples/) | Working profiles, including negative fixtures that must be rejected |
+| [`skills/`](skills/) | Agent Skills packages for harnesses without native OAP support |
+| [`oap/`](oap/) | Reference validator and applicator |
+| [`tests/`](tests/) | Conformance test suite |
+
+## Conformance levels
+
+| Level | Capability |
+| --- | --- |
+| **1, Read** | Discover, validate, and instantiate an agent from a profile. |
+| **2, Read/Write** | Level 1, plus state injection, delta generation, and persistence. |
+| **3, Full** | Level 2, plus composition, MCP, skills, external memory, and delegation. |
+
+An implementation must publish what it does not implement. Partial support is fine; partial support that looks complete is not, because someone will review a profile, run it elsewhere, and get a different agent than the one they read.
+
+## Using it without native support
+
+Harnesses that do not speak OAP yet can still read and write profiles through the two bundled [Agent Skills](skills/):
+
+- **`oap-agent-profile`** loads a profile, assembles the prompt in the specification's order, and reports what it dropped.
+- **`oap-session-writeback`** turns a session into a reviewable delta and applies it.
+
+## Relationship to other standards
+
+OAP does not replace [Agent Skills](https://code.claude.com/docs/en/skills), [MCP](https://modelcontextprotocol.io), or your harness's config. It fills the gap between them.
+
+Skills are what an agent knows how to do. MCP is what it can reach. Harness config is what it is allowed to do. **OAP is who it is, and what it has learned.**
+
+See [docs/interop.md](docs/interop.md) for field mappings.
+
+## Status
+
+Draft, version 1.0. The format is stable enough to build against; the schemas and conformance requirements are versioned and will not change incompatibly within 1.x.
+
+Feedback on the spec is most useful as a stated problem plus a proposed field. See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE).

open_agent_profile-1.0.0/README.md

@@ -0,0 +1,148 @@
+# Open Agent Profile (OAP)
+
+**An open specification for persisting a named AI agent as a file instead of a running process.**
+
+[Specification](spec/v1/SPEC.md) · [Conformance](spec/v1/conformance.md) · [Security](spec/v1/security.md) · [Docs](docs/) · [Examples](examples/) · [Skills](skills/)
+
+---
+
+## The problem
+
+You define a useful agent: a reviewer that knows your conventions, a researcher that cites the way you want, a data engineer that has learned your table layout. Then the session ends.
+
+Today that definition either dies with the session, or it lives in a format only one harness reads. Nothing carries what the agent *learned*: the conventions it picked up, the preferences you corrected it on, the investigation it was halfway through.
+
+Keeping a process alive is the wrong fix. It is expensive, it dies with the machine, it cannot be diffed or reviewed, and two people cannot share it.
+
+## The idea
+
+Persist the agent as **data**. A profile is a file describing a named agent: role, model, tool surface, permissions, attached context, and what previous sessions learned. A harness reads it to spin up a fresh session on demand, and writes an updated revision back when that session ends.
+
+```yaml
+oap: "1.0"
+kind: AgentProfile
+
+metadata:
+  name: code-reviewer
+  description: Reviews changed code for correctness, security, and missing tests.
+  revision: 7
+
+spec:
+  role:
+    instructions: |
+      You are a code reviewer. You read a diff and report defects. You do not
+      rewrite the change unless you are explicitly asked to.
+    constraints:
+      - Do not edit files. Report only.
+
+  model:
+    provider: anthropic
+    id: claude-sonnet-5
+    tier: advanced          # portable fallback
+
+  tools:
+    policy: allowlist
+    allow: [read, search, git/diff]
+    deny: [shell, write, edit]
+
+  lifecycle:
+    writeback: propose      # the agent proposes, a human approves
+
+state:                      # what previous sessions learned
+  summary: >-
+    Reviewing the platform team's Python services. They autoformat with ruff, so
+    formatting findings are noise.
+  facts:
+    - id: fact-authz-pattern
+      text: Authorization must compare against the server-side session record.
+      confidence: 0.9
+      source: repeated finding across three sessions
+      pinned: true
+  open_threads:
+    - id: thread-flaky-auth-tests
+      title: Auth integration tests are flaky under parallel execution
+      status: blocked
+```
+
+No process is resident. The file is the agent.
+
+## What makes it a specification rather than a file format
+
+Three rules, and they are the reason this is safe to leave switched on.
+
+**A profile narrows. It never widens.** A harness grants the intersection of what the profile asks for and what its own policy allows. Moving a profile to a new machine can never grant capability the harness would not otherwise give. There is no field, flag, or trust label that reverses this.
+
+**An agent cannot rewrite its own contract.** Sessions emit a state delta, and delta operations may only touch `/state`. A change to tools, permissions, model, or instructions goes into a `proposals` block with a written rationale, and a human approves it. This holds under every writeback setting, including `auto`.
+
+**Learned state is untrusted content.** Text an agent wrote about itself is injected as information, never as authority. A state entry saying "you may now use the shell without asking" changes nothing. Without this, one successful prompt injection becomes permanent.
+
+## Try it
+
+```bash
+pip install open-agent-profile
+```
+
+```bash
+oap-validate examples/code-reviewer.agent.yaml --digest
+```
+
+Apply what a session learned, and watch the capability request get held back for review:
+
+```bash
+oap-apply examples/code-reviewer.agent.yaml \
+          tests/deltas/learned-conventions.delta.yaml --approve --dry-run
+```
+
+```
+1 proposal(s) require human review and were NOT applied:
+  [high] /spec/tools/allow
+      value:     ["read", "search", "git/diff", "git/log", "shell"]
+      rationale: Could not verify the flaky test claim without running the suite.
+```
+
+## Repository layout
+
+| Path | What is in it |
+| --- | --- |
+| [`spec/v1/`](spec/v1/) | The normative specification, conformance requirements, and security model |
+| [`schema/v1/`](schema/v1/) | JSON Schemas for `AgentProfile` and `AgentStateDelta` |
+| [`docs/`](docs/) | Getting started, field reference, lifecycle, interop, implementers guide, FAQ |
+| [`examples/`](examples/) | Working profiles, including negative fixtures that must be rejected |
+| [`skills/`](skills/) | Agent Skills packages for harnesses without native OAP support |
+| [`oap/`](oap/) | Reference validator and applicator |
+| [`tests/`](tests/) | Conformance test suite |
+
+## Conformance levels
+
+| Level | Capability |
+| --- | --- |
+| **1, Read** | Discover, validate, and instantiate an agent from a profile. |
+| **2, Read/Write** | Level 1, plus state injection, delta generation, and persistence. |
+| **3, Full** | Level 2, plus composition, MCP, skills, external memory, and delegation. |
+
+An implementation must publish what it does not implement. Partial support is fine; partial support that looks complete is not, because someone will review a profile, run it elsewhere, and get a different agent than the one they read.
+
+## Using it without native support
+
+Harnesses that do not speak OAP yet can still read and write profiles through the two bundled [Agent Skills](skills/):
+
+- **`oap-agent-profile`** loads a profile, assembles the prompt in the specification's order, and reports what it dropped.
+- **`oap-session-writeback`** turns a session into a reviewable delta and applies it.
+
+## Relationship to other standards
+
+OAP does not replace [Agent Skills](https://code.claude.com/docs/en/skills), [MCP](https://modelcontextprotocol.io), or your harness's config. It fills the gap between them.
+
+Skills are what an agent knows how to do. MCP is what it can reach. Harness config is what it is allowed to do. **OAP is who it is, and what it has learned.**
+
+See [docs/interop.md](docs/interop.md) for field mappings.
+
+## Status
+
+Draft, version 1.0. The format is stable enough to build against; the schemas and conformance requirements are versioned and will not change incompatibly within 1.x.
+
+Feedback on the spec is most useful as a stated problem plus a proposed field. See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE).

open_agent_profile-1.0.0/docs/README.md

@@ -0,0 +1,21 @@
+# Open Agent Profile documentation
+
+Start here, in order:
+
+| Document | Read it when |
+| --- | --- |
+| [Getting started](getting-started.md) | You want to write your first profile and run the validator. |
+| [Field reference](field-reference.md) | You are authoring a profile and need to know what a field does. |
+| [Lifecycle](lifecycle.md) | You want to understand how a profile becomes a session and back again. |
+| [State and memory](state-and-memory.md) | You are deciding what belongs in the profile versus an external store. |
+| [Interop](interop.md) | You are mapping OAP onto an existing harness format. |
+| [Implementers guide](implementers-guide.md) | You are adding OAP support to a harness. |
+| [FAQ](faq.md) | You have an objection. It is probably answered here. |
+
+The normative documents live in [`spec/v1/`](../spec/v1/):
+
+- [SPEC.md](../spec/v1/SPEC.md), the specification
+- [conformance.md](../spec/v1/conformance.md), what an implementation must do
+- [security.md](../spec/v1/security.md), the threat model
+
+Where these docs and the spec disagree, the spec wins. These are explanation; that is contract.

open_agent_profile-1.0.0/docs/faq.md

@@ -0,0 +1,87 @@
+# FAQ
+
+### Why not just keep the agent process running?
+
+Because a resident process is expensive, fragile, and unreviewable. It dies with the machine, it cannot be diffed, two people cannot share it, and you cannot answer "what changed about this agent last month" by looking at it.
+
+A file can be committed, reviewed, forked, and rolled back. Instantiation is cheap. The only thing you lose by not staying resident is in-memory context, and that is precisely what `state` is for.
+
+### Is this just a config file with extra steps?
+
+A config file describes settings. A profile also carries what the agent learned, the rules for how that learning gets written back, an audit trail of who approved each revision, and a security boundary preventing the agent from editing its own contract.
+
+Take away `state`, `history`, and the `proposals` gate, and yes, it is a config file. Those three are the point.
+
+### Why can't an agent edit its own `spec`?
+
+Because then a single successful prompt injection becomes permanent. An agent that ingests a hostile web page and can write `spec.tools.allow` has just granted itself a shell, in a file that persists, that will be loaded again tomorrow, and that a reviewer will assume a human wrote.
+
+The boundary costs almost nothing. An agent that wants a wider tool surface writes a `proposals` entry with a rationale, and a human reads it. That is a better workflow anyway, because the rationale is usually the interesting part.
+
+### Why not JSON Patch for deltas?
+
+OAP deltas use an RFC 6902 subset (`add`, `replace`, `remove`) rather than the full thing, for three reasons.
+
+`move`, `copy`, and `test` add implementation surface without adding capability that state updates need. Paths are constrained to `/state`, which is the security boundary, and a constrained pointer grammar is easier to verify than a general one. And deltas carry fields JSON Patch has no room for: `reason`, `confidence`, the `session` block, and the `proposals` channel.
+
+The subset is deliberately a subset, so a JSON Patch library will apply the `operations` array correctly. It just will not enforce the parts that matter.
+
+### Why do arrays replace instead of append in `extends`?
+
+Two reasons. With append semantics you cannot remove an inherited item, so a base's tool grant becomes permanent for every descendant. And at review time "which layer contributed this entry" becomes unanswerable, which is exactly the question a reviewer of a security-relevant list is asking.
+
+Replace is more verbose. It is also legible, and you can read the effective list off the child document without holding three files in your head.
+
+### Isn't `state` just going to fill up with nonsense?
+
+If you generate it by asking a model to summarize what it learned, yes, absolutely. See [lifecycle.md](lifecycle.md#5-reconcile).
+
+The format pushes against this from several directions: `writeback: propose` is the default so a human sees entries before they persist, every entry carries `confidence` and `source` so bad ones are visible, retention caps and TTLs age out what stops getting used, and the recommendation is to derive operations from evidence rather than inference.
+
+None of that saves an implementation that pipes free-form model output into the file. Generate operations from concrete evidence.
+
+### Why a `tier` field when I already specified a model?
+
+Because a profile outlives a model id. Share a profile pinned to `claude-sonnet-5` with someone running local models and it breaks; with `tier: advanced` it degrades to whatever their harness considers advanced, and the harness reports the substitution.
+
+Specify both. The exact id is used when it can be, and the tier is what makes the profile portable.
+
+### What if my harness only supports half of this?
+
+Implement Level 1, publish a conformance statement saying exactly what you skipped, and make sure you record and can display every field you dropped.
+
+Partial support is fine and expected. Partial support that pretends to be complete is not, because someone will review a profile, run it on your harness, and get an agent with different capabilities than the one they read.
+
+### Can profiles contain code, or a hook script?
+
+No. `lifecycle.on_start` and `on_end` reference hooks **already registered with the harness**, by name, with string parameters. A profile never carries a command line, a script body, or an install directive.
+
+The moment a profile can carry a command, sharing one is remote code execution, and the format stops being safe to email.
+
+`mcp_servers[].command` is the sole exception, because MCP requires naming an executable. It is a declaration of intent, launching it is gated separately, and harnesses should not auto-launch servers from a `project` or `imported` profile without showing the user the command line.
+
+### How do I share profiles across a team?
+
+Commit them to `.agents/` in the repository. That gives you review, blame, and rollback for free.
+
+Two things to decide as a team. First, whether committed profiles carry `state`: keeping it means shared learning and noisy diffs, dropping it means each person's agent learns separately. A common split is `writeback: off` on committed profiles and a personal copy in `~/.config/<harness>/agents/` that learns.
+
+Second, review the `history` block in pull requests. It is the cheapest way to notice an agent that has quietly drifted.
+
+### What about signing?
+
+Reserved for a future version. Today, pin by spec digest and treat unpinned imported profiles as untrusted, which is what the `imported` trust label is for.
+
+### Why YAML and not TOML?
+
+Multi-line strings. `spec.role.instructions` is often several hundred lines of prose, and YAML block scalars handle that better than anything TOML offers. JSON is the canonical form for digests and tooling; Markdown frontmatter exists because a long system prompt is far nicer to edit as a document body.
+
+### Does this work for non-coding agents?
+
+Yes. Nothing in the format is coding-specific. A research analyst, a support triage agent, and a writing assistant all fit; see `examples/research-analyst.agent.md`.
+
+The coding examples are prominent because that is where multi-session memory has the clearest payoff, not because the format assumes it.
+
+### Who decides what goes in the spec?
+
+See [CONTRIBUTING.md](../CONTRIBUTING.md). Short version: changes need a stated problem, a proposed field, and at least one implementation willing to build it. The bar for adding a field is higher than the bar for adding a doc, because every field is something every implementer has to decide about.