@trigguard/protocol 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,8 +1,10 @@
|
|
|
1
|
-
#
|
|
1
|
+
# TrigGuard Protocol
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
[](https://www.npmjs.com/package/@trigguard/protocol)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Canonical protocol definitions for TrigGuard governance decisions: vocabulary (`PERMIT`, `DENY`, `SILENCE`), enforcement semantics, and the `DecisionRecord` shape used across products and tooling.
|
|
6
|
+
|
|
7
|
+
**Package name:** `@trigguard/protocol` — types and contract snapshots; runtime evaluation and policy engines live in other packages and services. Integrations **conform** to this contract.
|
|
6
8
|
|
|
7
9
|
## Install
|
|
8
10
|
|
|
@@ -10,9 +12,9 @@ The TrigGuard protocol defines the **contract for deterministic authorization de
|
|
|
10
12
|
npm install @trigguard/protocol
|
|
11
13
|
```
|
|
12
14
|
|
|
13
|
-
|
|
15
|
+
Published on the public registry under the `@trigguard` scope. For release process, see `docs/release/PROTOCOL_RELEASE.md` in the monorepo.
|
|
14
16
|
|
|
15
|
-
|
|
17
|
+
**Develop inside the repo** (no registry), use a path or workspace:
|
|
16
18
|
|
|
17
19
|
```json
|
|
18
20
|
"@trigguard/protocol": "file:../packages/protocol"
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@trigguard/protocol",
|
|
3
|
-
"version": "0.1.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.1.2",
|
|
4
|
+
"description": "Shared TypeScript types and JSON contract snapshots for TrigGuard authorization decisions and records.",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|
|
7
7
|
"exports": {
|