@alphazede/bearing-lite 0.1.0

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,45 @@
+# Code of Conduct
+
+## The short version
+
+Be decent to people. Argue about the work, not the person making it.
+
+## What we expect
+
+- Assume good faith, and give a clear reason when you disagree.
+- Accept that a maintainer may decline your idea. A no is not an insult.
+- Respect the boundaries of the project, including its security rules.
+- Keep other people's data out of issues, pull requests, and evidence you post.
+
+## What is not acceptable
+
+- Harassment, threats, or personal attacks of any kind.
+- Comments that demean someone for who they are rather than what they said.
+- Publishing private information, including someone's address, email, or
+  repository contents, without their permission.
+- Sustained disruption of a discussion after being asked to stop.
+
+## Where this applies
+
+Every space this project uses: issues, pull requests, discussions, commit
+messages, and any place where you are speaking for Bearing Lite.
+
+## Reporting
+
+Report a problem privately to the repository owner through GitHub. Do not open a
+public issue about someone's conduct, because that makes the situation worse for
+the person reporting it.
+
+If the report involves a security matter, use the [private vulnerability
+reporting form](https://github.com/alphazede/bearing-lite/security/advisories/new)
+instead. See [SECURITY.md](SECURITY.md).
+
+Reports are read by the maintainer and kept private. You will get a response.
+
+## What happens next
+
+Depending on what happened and whether it continues, the response ranges from a
+private word, to a warning, to removing comments, to blocking the account from
+the project. Serious or repeated behavior goes straight to a block.
+
+The maintainer makes these calls and is accountable for them.

package/CONTRIBUTING.md

@@ -0,0 +1,74 @@
+# Contributing to Bearing Lite
+
+## Provider-neutral public artifacts
+
+Packaged skills, hooks, manifests, and documentation must never require,
+select, recommend, or silently substitute a concrete agent, model, provider,
+or private harness alias for a role. Public guidance declares capabilities and
+independence requirements; the owner or compatible client maps available
+agents to those requirements. Client names may appear only to document a
+client-specific compatibility surface, never as a required implementation,
+coordination, fallback, or assurance route.
+
+Thanks for the interest. This page covers how the project works and what helps
+most.
+
+## How this repository works
+
+Bearing Lite is developed directly as a public skills-first Agent Plugin. The
+portable product surface is `plugin.json`, `skills/`, optional `hooks/`, and
+the public governance documents. There is no CLI binary, MCP server, browser
+control room, or hidden runtime state to maintain for ordinary contributions.
+
+Pull requests that stay inside that product boundary are welcome. Changes that
+reintroduce deep-harness coupling, model or provider pins, secret material, or
+private path spill will be declined.
+
+## Reporting a bug
+
+Open a bug report and include the Bearing Lite version (or commit), how you
+installed the plugin, your operating system, and which agent client you used.
+If a skill returned a structured handoff or a hook emitted a typed diagnostic,
+paste the sanitized text. Never include credentials, private repository
+contents, or unredacted session evidence.
+
+Never report a security problem in a public issue. Use the [private
+vulnerability reporting
+form](https://github.com/alphazede/bearing-lite/security/advisories/new).
+[SECURITY.md](SECURITY.md) covers what to include and what to leave out.
+
+## Proposing a change
+
+Open a feature request that states the problem before the solution. Bearing
+Lite is a bounded product: skills-first, provider-neutral, no telemetry, no
+hosted service, and no agent that certifies its own work. A proposal that
+crosses one of those lines is likely to be declined, and hearing that early
+saves you the work.
+
+## Working on the package
+
+Useful local checks for documentation and contract tests (when present in the
+checkout):
+
+```sh
+node --test test/diagram-sync.test.mjs
+node --test test/public-boundary.test.mjs
+node --test test/skills-conformance.test.mjs
+```
+
+Keep skills lean. Prefer references and assets only when progressive disclosure
+needs them. Do not add dependencies or change the lockfile without explicit
+maintainer approval. Do not add `mcp.json`, postinstall scripts, or global hook
+installers.
+
+When you change a Mermaid diagram under the plan assets or skill references,
+keep the paired PNG synchronized and preserve equivalent authoritative text
+(for task state, `skills/bearing-lite/references/task-state.md`).
+
+## What gets reviewed hardest
+
+Anything touching authority boundaries, independent assurance, public data
+spill, provider neutrality, hook fail-open versus integrity fail-closed
+behavior, or skill activation contracts. Those are the product rather than
+details of it, so expect questions and expect evidence that the change stays
+inside the approved Lite surface.

package/LICENSE-APACHE

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

package/README.md

@@ -0,0 +1,213 @@
+# Bearing Lite
+
+[![npm](https://img.shields.io/npm/v/@alphazede/bearing-lite)](https://www.npmjs.com/package/@alphazede/bearing-lite)
+[![license](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE-APACHE)
+
+**Bearing Lite** (`@alphazede/bearing-lite`) is a skills-first Agent Plugin for
+planning, routing, bounded execution, and independent review of repository work.
+It ships portable skills, references, templates, and optional client hooks. It
+does **not** ship a CLI, MCP server, browser control room, local scheduler, or
+hidden runtime database.
+
+An agent cannot certify its own work. The router selects the smallest valid
+route; independent assurance roles run only when declared, owner-selected, or
+required by a mandatory integrated phase gate. Owner Authority remains human-only.
+
+Bearing Lite was created by William Rumph at AlphaZede.
+
+## Install
+
+Install as an Agent Plugin in a compatible client (for example Codex or Claude
+Code marketplaces that discover Agent Plugins `plugin.json` and `skills/`).
+
+```sh
+# Example: npm package for packaging and inspection
+npm pack @alphazede/bearing-lite
+```
+
+Client install names follow the host plugin UI. The portable identity is always
+`bearing-lite` / `@alphazede/bearing-lite`. No postinstall script, global hook
+copy, or host-config mutation is required.
+
+Node.js is not required to *use* the skills. Optional typed hook adapters under
+`hooks/` run only when a client registers them; hookless clients remain
+first-class and use procedural skill checks.
+
+## What it does
+
+1. **Locate** the project plan and next ready task.
+2. **Fill only missing planning stages:** Repository Fit → Set Bearings → Gather
+   Supplies → Map the Route.
+3. **Choose the smallest role route** that preserves dependencies and
+   `required_assurance`.
+4. **Record task state** only in the project's human-readable plan (Markdown).
+5. **Return structured handoffs**; parent coordinators write plan transitions.
+
+Bearing Lite never selects models, providers, credentials, or launchers. The
+owner or client maps available agents to role capability needs.
+
+## Routes and scaling
+
+| Route | When | Cost |
+|---|---|---|
+| **Direct** | One bounded implementer packet | Lowest coordination |
+| **Explorer (wave)** | One wave, one or more Crewmates | One lane controller |
+| **Expedition** | Multi-phase or concurrent independent lanes | Navigator; Trail Boss only for concurrent/conflicting waves |
+| **Long multi-phase** | Owner-approved intent across sessions | Optional Delegate Authority |
+
+**Explorer** keeps one controller over a compact or sequential set of slices.
+**Expedition** adds navigation (and sometimes a Trail Boss) so independent lanes
+stay small and sharp instead of degrading in one long context. Either shape can
+use substantial tokens; the product does not impose a default budget ceiling.
+
+### Role routing (explanatory)
+
+![Bearing Lite role routing: Owner Authority and the router select missing planning stages, then the smallest route among Direct Crewmate, Explorer wave, Expedition Navigator, or long multi-phase Delegate Authority; optional Trail Boss, Sub-explorer, and assurance roles appear only when required](skills/bearing-lite/assets/role-routing.png)
+
+Reviewable Mermaid source: [`skills/bearing-lite/references/role-routing.mmd`](skills/bearing-lite/references/role-routing.mmd)
+(plan-local twin under `docs/plans/2026-08-09-bearing-skills-first-architecture/assets/`).
+
+**Authoritative text (vision optional):** Owner Authority remains human-only. The
+Bearing Lite Router is entry, not a work role. It invokes only missing planning
+stages, then picks the least costly route: Direct Crewmate; Explorer for one
+wave; Navigator for an expedition (Trail Boss only when waves conflict or run
+concurrently); Delegate Authority only for explicit long multi-phase owner
+delegation. Nested Sub-explorer opens only when a lane must split. After
+Crewmate work, `required_assurance: none` means author self-check plus
+coordinator confirmation; Validator, Park Ranger, and Surveyor appear only when
+listed, owner-selected at slice level, or required by a mandatory phase gate.
+Diagrams explain orientation; they never authorize a transition.
+
+## Roles and authority
+
+| Role | What it is | Executes | Notes |
+|---|---|---|---|
+| **Router** | Plugin entry procedure | no | Not a work role |
+| **Navigator** | Expedition orchestrator | yes | Owns cross-wave sequencing |
+| **Trail Boss** | Multi-wave controller | yes | Only concurrent or conflicting waves |
+| **Explorer** | One-wave lane controller | yes | Dispatches Crewmates |
+| **Sub-explorer** | Nested lane controller | yes | Only when a lane must split |
+| **Crewmate** | Bounded implementer | yes | Writes only inside declared authority |
+| **Validator** | Evidence sufficiency | yes | Independent of the author |
+| **Park Ranger** | Defect review | yes | Independent of the author |
+| **Surveyor** | User-facing acceptance | no | Read-only acceptance judgment |
+| **Delegate Authority** | Cross-session phase owner | yes | Only when owner explicitly delegates |
+| **Owner Authority** | Human decision | n/a | Never an agent role |
+
+**Independent review:** a candidate author never provides their own Validator,
+Park Ranger, or Surveyor verdict.
+
+Failure escalates to the nearest role whose scope can see it:
+
+| Failure scope | Escalates to |
+|---|---|
+| Within one slice or packet | Explorer or nearest parent |
+| Across slices in a wave | Trail Boss when present, else Navigator |
+| Across phases | Navigator or Delegate Authority |
+| Contract, security, or authority change | Owner Authority |
+
+## Task state (explanatory)
+
+![Bearing Lite task state machine: PROPOSED through READY, IN_PROGRESS, EVIDENCE_READY, optional VALIDATING or REVIEWING, ACCEPTANCE, COMPLETE, with WAITING_ON, CORRECTION_REQUIRED, OWNER_DECISION_REQUIRED, and CANCELLED paths](skills/bearing-lite/assets/task-state.png)
+
+Reviewable Mermaid source: [`skills/bearing-lite/references/task-state.mmd`](skills/bearing-lite/references/task-state.mmd).
+Authoritative transition rules: [`skills/bearing-lite/references/task-state.md`](skills/bearing-lite/references/task-state.md).
+
+**Authoritative summary:** The project's plan is the only task-state record.
+Normal progress is `PROPOSED` → `READY` → `IN_PROGRESS` → `EVIDENCE_READY`, then
+optional `VALIDATING` / `REVIEWING` when required, then `ACCEPTANCE` →
+`COMPLETE`. `WAITING_ON` holds for missing prerequisites or assurance dispatch.
+`CORRECTION_REQUIRED` allows two in-authority repairs; a third failed correction
+escalates to `OWNER_DECISION_REQUIRED`. Diagrams never create state or authorize
+transitions.
+
+## Implementation process (explanatory)
+
+Owner-approved multi-phase work follows four phases: Inventory, Foundation,
+Proof and Documentation, and Final Audit. Default slice completion is author
+self-check plus coordinator confirmation when `required_assurance` is `none`.
+Fresh Validator then separate Park Ranger is mandatory only on exact integrated
+phase candidates, not on every packet.
+
+![Bearing Lite implementation process: four phases with default self-check slices, optional owner slice assurance, mandatory integrated phase gates, bounded correction, and final Surveyor acceptance](docs/plans/2026-08-09-bearing-skills-first-architecture/assets/implementation-process.png)
+
+Mermaid source:
+[`docs/plans/2026-08-09-bearing-skills-first-architecture/assets/implementation-process.mmd`](docs/plans/2026-08-09-bearing-skills-first-architecture/assets/implementation-process.mmd).
+
+<details>
+<summary>Diagram source (implementation process)</summary>
+
+```mermaid
+flowchart TD
+    P1[Phase 1 Inventory S1-S4 complete] --> P2[Phase 2 Foundation S4A-S7]
+    P2 --> SLICE[Crewmate then author self-check]
+    SLICE --> CC[Coordinator scope and dependency confirmation]
+    CC --> OPT{Owner slice assurance?}
+    OPT -->|Yes| V[Fresh Validator then optional Park Ranger]
+    OPT -->|No| MORE{More Foundation slices?}
+    V -->|Fail or repair| R[Bounded Correction Attempt]
+    V -->|Pass| MORE
+    R -->|Attempt 1 or 2| SLICE
+    R -->|3rd Failure| O[OWNER_DECISION_REQUIRED]
+    MORE -->|Yes| SLICE
+    MORE -->|No: integrated Foundation| FG[Fresh Validator then separate Park Ranger]
+    FG --> P3[Phase 3 Proof and Documentation S8-S10]
+    P3 --> SLICE3[Crewmate then author self-check]
+    SLICE3 --> CC3[Coordinator confirmation]
+    CC3 --> OPT3{Owner slice assurance?}
+    OPT3 -->|Yes| V3[Fresh Validator then optional Park Ranger]
+    OPT3 -->|No| MORE3{More Proof and Documentation slices?}
+    V3 -->|Fail or repair| R
+    V3 -->|Pass| MORE3
+    MORE3 -->|Yes| SLICE3
+    MORE3 -->|No: integrated Proof and Documentation| PG[Fresh Validator then separate Park Ranger]
+    PG --> P4[Phase 4 Final Audit S11-S12]
+    P4 --> S11[S11 Skill and State Alignment Audit]
+    S11 --> S12[S12 Integrated Acceptance]
+    S12 --> S[Fresh Surveyor Final Acceptance]
+    S -->|Pass| CMP[COMPLETE]
+    O -->|Owner Decision| MORE
+```
+
+</details>
+
+## Package layout
+
+| Path | Purpose |
+|---|---|
+| `plugin.json` | Agent Plugins v1.0.0 manifest |
+| `skills/` | Router, planning stages, and role skills |
+| `hooks/` | Optional client-specific sequencing adapters |
+| `README.md` and governance docs | Public product and conduct surfaces |
+
+There is no `mcp.json`, `bin` entrypoint, postinstall, or runtime dependency on
+another product's state.
+
+## Provider neutrality
+
+Skills declare **capabilities** (reasoning depth, repository access, mutation
+tools, independence, optional vision). They never pin a model, provider API key,
+default route, or launcher. Owners and clients choose how to satisfy each role.
+
+## Migration note
+
+Bearing Lite does not import historical deep-harness run directories or hidden
+runtime state. Resume from the approved project plan and a verified
+human-readable handoff using native agent tools. See
+[guide/migration.md](guide/migration.md) for existing-run migration and
+owner distribution checkpoints.
+
+## Contributing
+
+Issues and carefully scoped pull requests help. See
+[CONTRIBUTING.md](CONTRIBUTING.md). Everyone is covered by the
+[Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Security
+
+Report suspected vulnerabilities privately—not in a public issue. See
+[SECURITY.md](SECURITY.md).
+
+## License
+
+Licensed under the [Apache License 2.0](LICENSE-APACHE).

package/SECURITY.md

@@ -0,0 +1,89 @@
+# Security Policy
+
+## Supported versions
+
+Bearing Lite is currently a pre-1.0 project. Security fixes are provided for the
+current `main` branch and the latest published `0.1.x` release of
+`@alphazede/bearing-lite`, when one is available. Older commits, development
+snapshots, and superseded releases are not supported unless a published advisory
+says otherwise.
+
+| Version | Supported |
+|---|---|
+| Current `main` | Yes |
+| Latest published `0.1.x` | Yes |
+| Older or superseded versions | No |
+
+## Report a vulnerability privately
+
+Use GitHub's [private vulnerability reporting
+form](https://github.com/alphazede/bearing-lite/security/advisories/new). Private
+vulnerability reporting is enabled for this repository when the host supports it.
+
+Do not open a public issue, discussion, pull request, or social-media post for
+a suspected vulnerability. Use [public
+issues](https://github.com/alphazede/bearing-lite/issues) only for ordinary,
+non-security bugs.
+
+Include enough information to reproduce and assess the problem:
+
+- The affected Bearing Lite version or commit.
+- Operating system, installation method, and agent client.
+- A minimal reproduction, proof of concept, and observed impact.
+- Whether owner authority, repository boundaries, skill routing, or hook
+  integrity behavior was bypassed or misreported.
+- Suggested mitigations, if known.
+
+Use synthetic data whenever possible. Do not send credentials, customer data,
+private repository contents, raw agent-session history, or unredacted evidence.
+If a secret may have been exposed, revoke or rotate it before reporting and
+include only a redacted identifier.
+
+## Security boundaries
+
+Reports are especially useful when they involve:
+
+- Skill or hook behavior that expands authority, skips required assurance, or
+  claims executable enforcement the client cannot provide.
+- Path traversal, unsafe file mutation guidance, or repository-boundary mistakes
+  in packaged skills or hooks.
+- Sensitive data leaking through logs, packaged files, diagnostics, or npm
+  package contents.
+- Release, dependency, build, or package-publishing integrity.
+- Model, provider, or credential handling introduced into public product
+  surfaces (Bearing Lite must remain provider-neutral and must not ship
+  credentials or secret lookup paths).
+
+A weakness in a third-party agent client, model provider, runtime, or dependency
+should normally be reported to that project. Report it to Bearing Lite as well
+when this package exposes, amplifies, or incorrectly handles the weakness.
+
+## Response and disclosure
+
+GitHub immediately records the private report. AlphaZede aims to:
+
+- Acknowledge the report within three business days.
+- Provide an initial triage result within seven calendar days.
+- Send an update at least every fourteen calendar days while remediation is
+  active.
+- Coordinate a fix, release, and public advisory before public disclosure when
+  the report is confirmed.
+
+These are response targets, not a support SLA. Timing may change with severity,
+reproduction quality, upstream dependencies, and release risk. Reporters who
+want public credit should request it in the private advisory. Duplicate,
+non-security, or unsupported reports will be closed with an explanation.
+
+## Good-faith research
+
+Research must avoid privacy violations, service disruption, persistence,
+social engineering, and access to data or repositories you do not own or have
+permission to test. Use the minimum access necessary, stop when sensitive data
+is encountered, and report promptly through the private channel.
+
+AlphaZede will not initiate legal action for accidental, good-faith violations
+of this policy when the researcher promptly stops, reports the issue, avoids
+harm, and gives reasonable time for remediation. This policy cannot authorize
+testing of third-party systems or excuse violations of applicable law.
+
+Bearing Lite does not currently offer a bug bounty or promise compensation.