tracelayer 0.1.0__tar.gz

tracelayer-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+.venv/
+__pycache__/
+*.pyc
+.trace/cache/
+.build/
+dist/
+build/
+.pytest_cache/
+.coverage
+htmlcov/
+.ruff_cache/
+.mypy_cache/
+node_modules/
+.serena/

tracelayer-0.1.0/AGENTS.md

@@ -0,0 +1,25 @@
+# TraceLayer
+
+Agent-native software traceability system. Python 3.12+ core, managed with `uv`.
+
+This repository uses mandatory semantic traceability. Trace integrity is part
+of the Definition of Done. Follow the repository traceability skill
+(`skills/traceability/SKILL.md`) and any trace instructions injected by hooks.
+
+Do not invent trace fields, replace stable IDs during refactors, or remove
+markers to silence validation. Before completing implementation work,
+`trace verify --changed` must pass under the active policy.
+
+Contributor workflow:
+
+```bash
+uv sync
+uv run pytest
+uv run ruff check .
+uv run trace --help
+```
+
+Generated docs (`docs/marker-protocol.md`, `docs/relationships.md`,
+`skills/traceability/references/marker-protocol.md`) are produced from the
+protocol registries; run `uv run trace docs generate` after changing the
+protocol and never edit them by hand.

tracelayer-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributing to TraceLayer
+
+TraceLayer is a deterministic traceability engine that sits in the coding-agent control loop. Small changes can alter marker parsing, staleness propagation, policy gates, or hook enforcement for every repository that adopts it. Contributions are welcome when they preserve the protocol invariants and include evidence for the behavior they change.
+
+Read [AGENTS.md](AGENTS.md) for repository-specific engineering rules. The normative specification is [traceability-system-master-spec.md](traceability-system-master-spec.md); generated documentation must come from the registries, never be hand-edited.
+
+## Development setup
+
+### Prerequisites
+
+- Git
+- Python `3.12+`
+- [`uv`](https://docs.astral.sh/uv/) — dependency management is uv-only
+
+```bash
+git clone https://github.com/carterlasalle/tracelayer.git
+cd tracelayer
+uv sync
+```
+
+Confirm the baseline before editing:
+
+```bash
+uv run pytest
+uv run ruff check .
+uv run trace docs generate --check
+```
+
+## Repository rules
+
+- **Deterministic before semantic.** If a fact can be proven by parsing, Git, file existence, tests, or coverage, the engine must prove it. Never spend an LLM on it, and never hand an LLM the job of the deterministic engine.
+- **One canonical schema.** The marker grammar, ontology, and TL-rule registries in `src/tracelayer/protocol/` and `src/tracelayer/diagnostics.py` are the single source of truth. `docs/marker-protocol.md`, `docs/relationships.md`, and `skills/traceability/references/marker-protocol.md` are generated — run `uv run trace docs generate` after changing the protocol and never edit them by hand.
+- **Every failure is explainable.** Diagnostics come from the rule registry (`tracelayer.diagnostics.make`) with severity and remediation. Recoverable input problems are diagnostics, never exceptions.
+- **Trace integrity is part of the Definition of Done.** Before completing implementation work, `trace verify --changed` must pass under the active policy.
+- **Derived facts are never declared.** Paths, line numbers, commit SHAs, test results, and structural/observed edges must not appear in markers.
+- **Ambiguity fails loudly.** A parser that cannot decide reports TL003; it never attaches a marker to a guessed symbol.
+
+## Pull requests
+
+- Protected, squash-only pull requests with required checks.
+- Every PR must include tests for the behavior it changes and update generated reference docs when the protocol changes.
+- Use the [pull request template](.github/pull_request_template.md): list affected trace IDs, summarize the change, and check the verification boxes.
+- New observable contracts (CLI flags, JSON shapes, rule behavior) get a focused test — see `tests/integration/test_dod_gaps.py` for the pattern.
+
+## Development commands
+
+```bash
+uv run pytest                      # full suite (709 tests)
+uv run pytest tests/unit/protocol -q   # scoped runs work too
+uv run ruff check .                # lint; fix with uv run ruff check --fix .
+uv run trace --help                # CLI smoke
+uv run trace docs generate --check # protocol docs drift check
+```
+
+## Testing conventions
+
+- Deterministic only: `tmp_path` fixtures, no network, no wall-clock dependence. Normalize timestamps and SHAs in golden outputs.
+- Shared fixtures live in `tests/conftest.py` (`make_git_repo`, `run_trace`).
+- Property tests use Hypothesis (`tests/unit/protocol/test_property.py`).
+- Hook behavior is tested by simulating harness events as JSON; no harness is required.
+- The repository traces itself: add `trace:v1` markers to meaningful behavior boundaries you create, then run `uv run trace verify --changed`.

tracelayer-0.1.0/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 TraceLayer 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.

tracelayer-0.1.0/PKG-INFO

@@ -0,0 +1,230 @@
+Metadata-Version: 2.5
+Name: tracelayer
+Version: 0.1.0
+Summary: TraceLayer: agent-native software traceability system
+Project-URL: Homepage, https://github.com/carterlasalle/tracelayer
+Project-URL: Repository, https://github.com/carterlasalle/tracelayer
+Project-URL: Issues, https://github.com/carterlasalle/tracelayer/issues
+Project-URL: Documentation, https://github.com/carterlasalle/tracelayer#documentation
+Author: carterlasalle
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,ci,cli,requirements,software-engineering,traceability
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.12
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: tree-sitter-language-pack>=0.3
+Requires-Dist: tree-sitter>=0.23
+Requires-Dist: typer>=0.12
+Description-Content-Type: text/markdown
+
+<div align="center">
+
+# TraceLayer
+
+**Agent-native software traceability: intent, implementation, verification, provenance, and evidence as a deterministic graph.**
+
+[![CI](https://img.shields.io/github/actions/workflow/status/carterlasalle/tracelayer/trace.yml?branch=master&label=CI)](https://github.com/carterlasalle/tracelayer/actions/workflows/trace.yml)
+![Python](https://img.shields.io/badge/Python-3.12%2B-3776AB?logo=python&logoColor=white)
+![uv](https://img.shields.io/badge/uv-managed-884AA8?logo=python&logoColor=white)
+![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)
+![Tests](https://img.shields.io/badge/tests-709%20passing-brightgreen)
+
+[Marker protocol](docs/marker-protocol.md) · [Relationships](docs/relationships.md) · [Concepts](docs/concepts.md) · [Policy](docs/policy.md) · [Hooks](docs/hooks.md) · [Evidence](docs/evidence.md) · [Security](docs/security.md)
+
+</div>
+
+TraceLayer makes the **why** of software traversable. One-line `trace:v1` markers declare the semantic relationships that cannot be derived — which work item produced a behavior, which requirement it satisfies, which tests intend to verify it. The engine derives everything else: AST symbol attachment, Git provenance, revision fingerprints, staleness, and runtime evidence. The result is a continuously verified trace graph that agents and reviewers can query instead of loading the whole repository.
+
+## How it works
+
+```mermaid
+flowchart LR
+    A[trace:v1 markers] --> B[Marker parser]
+    B --> C[AST symbol attachment]
+    C --> D[SQLite trace graph]
+    D --> E[Git provenance]
+    E --> F[Fingerprints and staleness]
+    F --> G[Policy evaluation]
+    D --> H[Query engine]
+    H --> I[context / why / impact / search]
+    G --> J[Verify gate]
+    J --> K[Hook engine]
+    K --> L[Agent context and Stop gate]
+    L --> M[CI merge gate]
+```
+
+Markers are the authoring notation; the graph is the product. Paths, line numbers, commit SHAs, and test results are derived — never written into markers — so trace identity survives refactors and evidence can never silently go stale.
+
+## Capabilities
+
+| Area | What TraceLayer provides |
+|---|---|
+| Protocol | One-line versioned `trace:v1` grammar, typed semantic edges, stable IDs, deterministic type inference, generated schema docs |
+| Indexing | Full and changed-scope indexing, Markdown/YAML artifact extraction, fence-aware marker scanning, honest file-level degradation for unsupported languages |
+| Symbols | Tree-sitter attachment for Python, TypeScript, JavaScript, Go, Rust, and Java — markers attach to symbols, never line numbers |
+| Graph | SQLite materialized index with declared, structural (`contains`), and observed (`executed`) provenance; FTS5 search; bounded traversal |
+| Provenance | Git-derived first-seen/last-modified history, rename tracking, changed-line ranges, dirty-tree status — no commit IDs in source |
+| Staleness | Requirement/implementation fingerprints, upstream-change propagation, review states, historical evidence preservation |
+| Policy | Four profiles (minimal/standard/strict/safety-critical) across five lifecycles, scoped expiring waivers, deterministic TL-rule registry |
+| Query UX | `context`, `why`, `impact`, `search`, `graph` (tree/mermaid/DOT/JSON/JSONL), `status`, `doctor`, `report pr` |
+| Hooks | Session start, prompt context, pre-mutation block-once guard, post-mutation guidance, batch summary, fail-closed Stop gate |
+| Evidence | JUnit/Cobertura/normalized ingestion, revision binding, L0–L3 proof levels, per-test Python coverage adapter |
+| Migration | CodeOps scan/plan/apply with deterministic classification, Scry detection, doctor diagnostics with rename suggestions |
+| Audit | Bounded deterministic audit packages for an independent semantic reviewer — no LLM required for the engine itself |
+
+## Quick start
+
+### Install
+
+From the repository (no publish step needed):
+
+```bash
+uv tool install git+https://github.com/carterlasalle/tracelayer.git
+trace --help
+```
+
+Or install from a local checkout: `uv tool install .`. The wheel is verified
+against a clean venv with `uv build`; a PyPI publish is the planned next step.
+
+The first time you run `trace` outside a configured repository it prints
+next steps: `trace init` to enable traceability in the current repo, or
+`trace install` to install the skill and hooks into your agent harnesses
+globally. Set `TRACE_NO_HINT=1` to silence that message (e.g. in CI).
+
+### Publishing
+
+`tracelayer` is published to PyPI on version tags via trusted publishing
+(no tokens stored in CI). Publish a release with:
+
+```bash
+git tag v0.1.0 && git push origin v0.1.0
+```
+
+Manual publish from a checkout: `uv build && uv publish`. See
+`.github/workflows/release.yml` for the one-time PyPI trusted-publisher
+setup.
+
+### Prerequisites
+
+- Python `3.12+`
+- [`uv`](https://docs.astral.sh/uv/) (dependency management is uv-only; no pip)
+
+```bash
+uv sync
+uv run trace --help
+```
+
+Trace an existing repository:
+
+```bash
+uv run trace init --root <repo>          # writes .trace/trace.toml + policy.toml
+uv run trace index --root <repo> --all
+uv run trace verify --root <repo> --all
+uv run trace context --root <repo> <trace-id>
+```
+
+Run the full development baseline:
+
+```bash
+uv run pytest
+uv run ruff check .
+uv run trace docs generate --check
+```
+
+## Architecture
+
+TraceLayer is a single Python package with deliberately narrow module boundaries:
+
+```text
+src/tracelayer/
+  cli.py                   Typer CLI; business logic lives in modules
+  engine.py                Indexing pipeline, verify, staleness, TraceRepository API
+  config.py                trace.toml / policy.toml models and loading
+  diagnostics.py           TL-rule registry; every failure carries remediation
+  protocol/                Marker grammar, parser, ID rules, ontology, generated schema
+  discovery/               File enumeration, ignore logic, monorepo scopes
+  artifacts/               Markdown, YAML, and generic file-level extraction
+  symbols/                 Tree-sitter parsers and marker-to-symbol attachment
+  graph/                   Node/edge models, SQLite store, migrations, traversal, fingerprints
+  git/                     Provenance, history, diff-range mapping (argv-array subprocess only)
+  evidence/                JUnit, Cobertura, normalized JSON, freshness, proof levels
+  policy/                  Profiles, lifecycle, waivers, deterministic rule functions
+  query/                   context, why, impact, search
+  hooks/                   Event handlers and file-backed session state
+  audit/                   Bounded semantic-audit packages and external auditor adapter
+  migration/               CodeOps and Scry importers
+```
+
+Every module is independently testable; the CLI is a thin shell over the engine.
+
+## Safety model
+
+TraceLayer sits in the coding-agent control loop, so correctness is fail-closed by construction:
+
+- Declared claims are never displayed as proven: a `test -> exercises -> implementation` claim stays unproven until observed execution evidence exists (proof levels L0–L3).
+- Derived facts cannot be declared: paths, SHAs, test results, and structural/observed edges are rejected in markers.
+- Ambiguity is a diagnostic, never a silent guess: detached markers, unresolved targets, and duplicate IDs are deterministic TL failures with remediation.
+- Staleness preserves history: changing a requirement marks downstream review-required; it never deletes evidence.
+- Repository text is untrusted data: hooks inject bounded, sanitized summaries; subprocess calls use argv arrays; no `shell=True`.
+- Policy can weaken only deliberately: enforcement-file changes surface as TL063 warnings; waivers are scoped, owned, and expiring.
+- CI and the Stop gate run the same engine as the CLI — there is no separate enforcement code path.
+
+## Documentation
+
+| Document | Purpose |
+|---|---|
+| [Concepts](docs/concepts.md) | Three truths, the trace graph, stable IDs, staleness |
+| [Marker protocol](docs/marker-protocol.md) | Generated normative `trace:v1` syntax and placement rules |
+| [Relationships](docs/relationships.md) | Generated semantic/structural/observed edge semantics |
+| [Policy](docs/policy.md) | Profiles, lifecycles, waivers, and the TL-rule catalog |
+| [Hooks](docs/hooks.md) | Event model, block-once semantics, injection safety |
+| [Evidence](docs/evidence.md) | JUnit/Cobertura ingestion and proof levels L0–L3 |
+| [Migration](docs/migration-codeops.md) | CodeOps scan/plan/apply workflow |
+| [Security](docs/security.md) | Threat model and mitigations |
+| [Large repositories](docs/large-repos.md) | Incremental indexing, monorepo scopes, performance targets |
+| [Architecture decisions](docs/adr/) | ADR-0001 through ADR-0008 |
+
+## Installing the agent skill
+
+The canonical skill (canonical layout: `SKILL.md` + `README.md` +
+`references/`) lives in [`skills/traceability/`](skills/traceability/README.md)
+and is bundled with the installed package. Install it with `trace install`:
+
+```bash
+trace install --list                     # detect agents and install state
+trace install --agent claude-code        # project scope (.claude/skills)
+trace install --agent claude-code --global --yes   # ~/.claude/skills
+trace install --yes                      # all detected agents, non-interactive
+```
+
+Hooks are merged for claude-code (`.claude/settings.json`) and codex
+(`.codex/hooks.json`) in project scope; other agents get the skill only —
+see `adapters/<harness>/README.md` for their hook setup. The same skill is
+installable through the skills.sh ecosystem:
+
+```bash
+npx skills add carterlasalle/tracelayer --agent claude-code
+```
+
+For existing repositories, `trace init --skill` copies the skill into
+`.agents/skills/traceability/` directly. The same folder is ready for skill
+registries (e.g. skills.sh, anthropics/skills) — it follows the standard
+layout and links references directly from `SKILL.md`.
+
+## Contributing
+
+TraceLayer uses protected, squash-only pull requests with required checks. Read [CONTRIBUTING.md](CONTRIBUTING.md) before making changes. Run `uv run trace docs generate --check` when editing protocol documentation and `trace verify --changed` before proposing a merge — this repository traces itself.
+
+## License
+
+Apache License 2.0 — see [LICENSE](LICENSE).