From 983f0895a48f97b82cb6f948ed63c1cdc6a72cd1 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 24 Mar 2026 01:22:50 +0000 Subject: [PATCH 1/2] Initial plan From 9eacb7c3c5f2632dbdfdafa0f68b9c4417d4372f Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 24 Mar 2026 01:25:28 +0000 Subject: [PATCH 2/2] fix(docs): replace machine-local absolute paths with repo-relative links Co-authored-by: chrismaz11 <24700273+chrismaz11@users.noreply.github.com> Agent-Logs-Url: https://github.com/TrustSignal-dev/TrustSignal/sessions/35280d20-7331-4aa8-b04d-6a90e473db17 --- COPYRIGHT.md | 6 +++--- bench/README.md | 6 +++--- wiki/API-Overview.md | 14 +++++++------- wiki/Home.md | 10 +++++----- wiki/Quick-Verification-Example.md | 10 +++++----- wiki/What-is-TrustSignal.md | 2 +- 6 files changed, 24 insertions(+), 24 deletions(-) diff --git a/COPYRIGHT.md b/COPYRIGHT.md index 93083e7..0155906 100644 --- a/COPYRIGHT.md +++ b/COPYRIGHT.md @@ -10,7 +10,7 @@ This repository is maintained as proprietary TrustSignal software and documentat ## Repository Consistency Rules -- Root ownership and license notices must remain consistent with the proprietary repository license in [`LICENSE`](/Users/christopher/Projects/TrustSignal/LICENSE). +- Root ownership and license notices must remain consistent with the proprietary repository license in [`LICENSE`](LICENSE). - File-level license headers that conflict with the repository ownership position must be reviewed deliberately and documented before they are included in any ownership or registration claim. - If a contribution was created with material AI assistance, external templates, copied snippets, contractor input, or third-party source material, that provenance must be recorded before the file is treated as a registration candidate. @@ -31,10 +31,10 @@ The following categories are excluded from the initial copyright registration ca ## Open License Decision -- [`packages/contracts/contracts/AnchorRegistry.sol`](/Users/christopher/Projects/TrustSignal/packages/contracts/contracts/AnchorRegistry.sol) currently carries an `Apache-2.0` SPDX header. +- [`packages/contracts/contracts/AnchorRegistry.sol`](packages/contracts/contracts/AnchorRegistry.sol) currently carries an `Apache-2.0` SPDX header. - That file must be treated as a deliberate license-decision item and excluded from the initial proprietary registration bundle until its licensing intent is explicitly resolved. ## Notices and Attribution -- If you add third-party code or assets, include any required attribution or notice material in [`NOTICE`](/Users/christopher/Projects/TrustSignal/NOTICE) or in file-level notices as appropriate. +- If you add third-party code or assets, include any required attribution or notice material in [`NOTICE`](NOTICE) or in file-level notices as appropriate. - Do not remove or alter third-party license notices without confirming the applicable license obligations. diff --git a/bench/README.md b/bench/README.md index 7417b53..f284619 100644 --- a/bench/README.md +++ b/bench/README.md @@ -31,8 +31,8 @@ npx tsx bench/run-bench.ts --scenario batch --batch-size 10 The harness writes: -- [latest.json](/Users/christopher/Projects/trustsignal/bench/results/latest.json) -- [latest.md](/Users/christopher/Projects/trustsignal/bench/results/latest.md) +- [latest.json](results/latest.json) +- [latest.md](results/latest.md) The JSON contains raw timings plus aggregate metrics. The Markdown report is the public-safe evaluator summary for docs. @@ -40,5 +40,5 @@ The JSON contains raw timings plus aggregate metrics. The Markdown report is the - The harness starts a temporary local PostgreSQL instance and tears it down after the run. - It targets the real local `/api/v1/*` evaluator routes through Fastify injection, so it exercises the same request validation, auth checks, persistence, receipt issuance, and later-verification logic used by the current evaluator path. -- It uses local fixture artifacts from [bench/fixtures](/Users/christopher/Projects/trustsignal/bench/fixtures) to keep clean and tampered runs deterministic. +- It uses local fixture artifacts from [bench/fixtures](fixtures) to keep clean and tampered runs deterministic. - Current metrics are local benchmark snapshots, not production guarantees. diff --git a/wiki/API-Overview.md b/wiki/API-Overview.md index 18fb696..f55cc5a 100644 --- a/wiki/API-Overview.md +++ b/wiki/API-Overview.md @@ -17,7 +17,7 @@ Partners need a stable public contract that explains how TrustSignal fits into a ## Verification Lifecycle -The canonical lifecycle diagram is documented in [docs/verification-lifecycle.md](/Users/christopher/Projects/trustsignal/docs/verification-lifecycle.md). +The canonical lifecycle diagram is documented in [docs/verification-lifecycle.md](../docs/verification-lifecycle.md). TrustSignal exposes a public verification lifecycle centered on signed verification receipts, verification signals, verifiable provenance metadata, and later verification. @@ -25,16 +25,16 @@ TrustSignal exposes a public verification lifecycle centered on signed verificat Start with the local developer trial for the fastest lifecycle walkthrough: -- [5-minute developer trial](/Users/christopher/Projects/trustsignal/demo/README.md) +- [5-minute developer trial](../demo/README.md) ## Integration Model Start here to try the public lifecycle: -- [OpenAPI contract](/Users/christopher/Projects/trustsignal/openapi.yaml) -- [Evaluator quickstart](/Users/christopher/Projects/trustsignal/docs/partner-eval/quickstart.md) -- [API playground](/Users/christopher/Projects/trustsignal/docs/partner-eval/api-playground.md) -- [Postman collection](/Users/christopher/Projects/trustsignal/postman/TrustSignal.postman_collection.json) +- [OpenAPI contract](../openapi.yaml) +- [Evaluator quickstart](../docs/partner-eval/quickstart.md) +- [API playground](../docs/partner-eval/api-playground.md) +- [Postman collection](../postman/TrustSignal.postman_collection.json) Golden path: @@ -103,4 +103,4 @@ Integrators should expect these broad patterns: - `429` for rate limiting - `503` when a required dependency is unavailable -The canonical public contract for the verification lifecycle is [openapi.yaml](/Users/christopher/Projects/trustsignal/openapi.yaml). +The canonical public contract for the verification lifecycle is [openapi.yaml](../openapi.yaml). diff --git a/wiki/Home.md b/wiki/Home.md index 0ff9b5b..19b66a0 100644 --- a/wiki/Home.md +++ b/wiki/Home.md @@ -21,7 +21,7 @@ High-loss environments create incentives for these attack paths because downstre ## Verification Lifecycle -The canonical lifecycle diagram is documented in [docs/verification-lifecycle.md](/Users/christopher/Projects/trustsignal/docs/verification-lifecycle.md). +The canonical lifecycle diagram is documented in [docs/verification-lifecycle.md](../docs/verification-lifecycle.md). TrustSignal provides signed verification receipts, verification signals, verifiable provenance metadata, and later verification capability as an integrity layer for an existing system of record. @@ -35,15 +35,15 @@ TrustSignal provides signed verification receipts, verification signals, verifia ## Demo -- [5-minute developer trial](/Users/christopher/Projects/trustsignal/demo/README.md) +- [5-minute developer trial](../demo/README.md) ## Integration Model Use the evaluator docs when you want to see the verification lifecycle before production integration detail: -- [Evaluator quickstart](/Users/christopher/Projects/trustsignal/docs/partner-eval/quickstart.md) -- [API playground](/Users/christopher/Projects/trustsignal/docs/partner-eval/api-playground.md) -- [OpenAPI contract](/Users/christopher/Projects/trustsignal/openapi.yaml) +- [Evaluator quickstart](../docs/partner-eval/quickstart.md) +- [API playground](../docs/partner-eval/api-playground.md) +- [OpenAPI contract](../openapi.yaml) ## Technical Details diff --git a/wiki/Quick-Verification-Example.md b/wiki/Quick-Verification-Example.md index 1283e73..66f1444 100644 --- a/wiki/Quick-Verification-Example.md +++ b/wiki/Quick-Verification-Example.md @@ -17,7 +17,7 @@ This example is for partner engineers who want the smallest realistic TrustSigna ## Verification Lifecycle -The canonical lifecycle diagram is documented in [docs/verification-lifecycle.md](/Users/christopher/Projects/trustsignal/docs/verification-lifecycle.md). +The canonical lifecycle diagram is documented in [docs/verification-lifecycle.md](../docs/verification-lifecycle.md). This example uses the current integration-facing lifecycle to create a verification, return verification signals plus a signed verification receipt, store the receipt with the workflow record, and later verify stored receipt state during audit review. @@ -25,10 +25,10 @@ This example uses the current integration-facing lifecycle to create a verificat Start here for the full evaluator path: -- [Evaluator quickstart](/Users/christopher/Projects/trustsignal/docs/partner-eval/quickstart.md) -- [API playground](/Users/christopher/Projects/trustsignal/docs/partner-eval/api-playground.md) -- [OpenAPI contract](/Users/christopher/Projects/trustsignal/openapi.yaml) -- [Postman collection](/Users/christopher/Projects/trustsignal/postman/TrustSignal.postman_collection.json) +- [Evaluator quickstart](../docs/partner-eval/quickstart.md) +- [API playground](../docs/partner-eval/api-playground.md) +- [OpenAPI contract](../openapi.yaml) +- [Postman collection](../postman/TrustSignal.postman_collection.json) ## Integration Model diff --git a/wiki/What-is-TrustSignal.md b/wiki/What-is-TrustSignal.md index 583fa0e..e69040c 100644 --- a/wiki/What-is-TrustSignal.md +++ b/wiki/What-is-TrustSignal.md @@ -25,7 +25,7 @@ TrustSignal is evidence integrity infrastructure. It provides signed verificatio The fastest local evaluator path is the 5-minute developer trial: -- [5-minute developer trial](/Users/christopher/Projects/trustsignal/demo/README.md) +- [5-minute developer trial](../demo/README.md) ## Integration