@ttsc/evidence 0.28.2 → 0.28.4

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.
Files changed (2) hide show
  1. package/README.md +13 -12
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -4,19 +4,20 @@
4
4
 
5
5
  [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/samchon/ttsc/blob/master/LICENSE) [![NPM Version](https://img.shields.io/npm/v/@ttsc/evidence.svg)](https://www.npmjs.com/package/@ttsc/evidence) [![NPM Downloads](https://img.shields.io/npm/dm/@ttsc/evidence.svg)](https://www.npmjs.com/package/@ttsc/evidence) [![Build Status](https://github.com/samchon/ttsc/actions/workflows/build.yml/badge.svg)](https://github.com/samchon/ttsc/actions/workflows/build.yml) [![Guide Documents](https://img.shields.io/badge/Guide-Documents-forestgreen)](https://ttsc.dev/docs/evidence) [![Discord Badge](https://img.shields.io/badge/discord-samchon-d91965?style=flat&labelColor=5866f2&logo=discord&logoColor=white&link=https://discord.gg/E94XhzrUCZ)](https://discord.gg/E94XhzrUCZ)
6
6
 
7
- A coding agent can claim it followed every requirement while silently skipping some. Finding those omissions means rereading the specification, implementation, and tests until another review round finds nothing new.
7
+ Every specification becomes a compile-time obligation.
8
8
 
9
- Evidence Graph replaces that loop with compile-time obligations. You declare which artifacts owe which specification units. The agent cites each unit from the code, test, schema, or document that satisfies it and states why. An unanswered unit is a compile error.
9
+ Citing the evidence and describing the reason why are mandatory, so you get:
10
10
 
11
- Evidence Graph can also require the agent to state how each function follows project-wide principles. "No hard coding" and "Fix root causes" then become explicit obligations on every selected function.
11
+ - **100% coverage** of every requirement.
12
+ - **100% compliance** with every principle.
12
13
 
13
14
  ```tsx
14
15
  /**
15
16
  * @evidence docs/discount.md#coupon-stacking States the per-issuer stacking limit this section defines, in the buyer's words.
16
17
  * @evidence POST:/orders/{orderId}/coupons Explains the rejection this endpoint returns for an over-stacked coupon set.
17
18
  * @evidence {@link hooks.useCouponStacking} Renders the limit this hook resolves.
18
- * @evidence docs/principles.md#no-hard-coding Renders limits from props instead of branching on known issuer names.
19
- * @evidenceExclude docs/principles.md#fix-root-causes-not-symptoms No failure to fix.
19
+ * @evidence .agents/skills/principles/SKILL.md#no-hard-coding Renders limits from props instead of branching on known issuer names.
20
+ * @evidenceExclude .agents/skills/principles/SKILL.md#fix-root-causes-not-symptoms No failure to fix.
20
21
  */
21
22
  export function CouponStackingNotice(props: IProps): JSX.Element;
22
23
  ```
@@ -40,7 +41,7 @@ error TS16411: [evidence/graph] Missing acknowledgement for 'docs/discount.md#co
40
41
 
41
42
  ...
42
43
 
43
- Found 3 errors.
44
+ Found 5 errors.
44
45
  ```
45
46
 
46
47
  Missing obligations appear in the same build as type errors. The error list is the agent's task list.
@@ -106,7 +107,7 @@ export default {
106
107
 
107
108
  One claim: the components under `src` implement the docs, so every H2 and H3 under `docs` must be cited by a component. Run `npx ttsc` and the error count is the backlog.
108
109
 
109
- [The rule reference](https://ttsc.dev/docs/evidence/rules) has four more rules beside `evidence/graph`, and [the claim reference](https://ttsc.dev/docs/evidence/claims) has every claim option.
110
+ [The configuration reference](https://ttsc.dev/docs/evidence/claims) has every claim option and the four rules beside `evidence/graph`.
110
111
 
111
112
  ### Tags
112
113
 
@@ -146,7 +147,7 @@ Backend, frontend, and even novels below are this same shape, drawn in detail.
146
147
 
147
148
  ### Start with principles
148
149
 
149
- Spec-Driven Development does not require a complete document hierarchy. `docs/principles.md` can be only headings:
150
+ 100% compliance with every principle.
150
151
 
151
152
  ```md
152
153
  ## No hard coding
@@ -165,7 +166,7 @@ Make them a checklist:
165
166
  symbol: "function",
166
167
  reference: {
167
168
  type: "markdown",
168
- files: ["docs/principles.md"],
169
+ files: [".agents/skills/principles/SKILL.md"],
169
170
  symbol: "h2",
170
171
  checklist: true,
171
172
  requireReview: true,
@@ -205,7 +206,7 @@ Screens and journeys also cite the documents, so every screen traces back to a r
205
206
 
206
207
  ### Novels
207
208
 
208
- <picture><source media="(prefers-color-scheme: dark)" srcset="https://ttsc.dev/evidence/novel-dark.svg"><img alt="Principles and Settings grounding Storylines, Scenarios and Manuscripts" src="https://ttsc.dev/evidence/novel-light.svg" width="100%"></picture>
209
+ <picture><source media="(prefers-color-scheme: dark)" srcset="https://ttsc.dev/evidence/novel-dark.svg"><img alt="Principles and Settings grounding Treatments, Scripts and Prose" src="https://ttsc.dev/evidence/novel-light.svg" width="100%"></picture>
209
210
 
210
211
  > Real config: [`napoleon-imperator/lint.config.ts`](https://github.com/samchon/novels/blob/master/packages/napoleon-imperator/lint.config.ts)
211
212
 
@@ -213,8 +214,8 @@ The graph reads no meaning, only obligations and citations, so it works on any t
213
214
 
214
215
  - Every layer cites the principles for its literary purpose.
215
216
  - Every layer cites the settings for facts, rules, and knowledge.
216
- - Scenarios and manuscripts cite storylines for cause and consequence.
217
- - A manuscript cites the scenario it executes, exactly.
217
+ - Scripts and prose cite treatments for cause and consequence.
218
+ - Prose cites the script it executes, exactly.
218
219
 
219
220
  Editing a setting expires every review on it, so a revision leaves no stale scene behind. [`samchon/novels`](https://github.com/samchon/novels) runs this graph on 25 principles, 350 setting commitments, and 742 scenes.
220
221
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ttsc/evidence",
3
- "version": "0.28.2",
3
+ "version": "0.28.4",
4
4
  "description": "Evidence-graph lint contributor for @ttsc/lint: declare provenance with a JSDoc @evidence tag and fail the build when it is missing or dangling.",
5
5
  "main": "lib/index.js",
6
6
  "exports": {
@@ -48,8 +48,8 @@
48
48
  "@types/node": "^25.3.0",
49
49
  "rimraf": "^6.1.2",
50
50
  "typescript": "^7.0.2",
51
- "@ttsc/lint": "0.28.2",
52
- "ttsc": "0.28.2"
51
+ "@ttsc/lint": "0.28.4",
52
+ "ttsc": "0.28.4"
53
53
  },
54
54
  "dependencies": {
55
55
  "@prisma/prisma-schema-wasm": "7.10.0-2.d0368e25c88e68caa4d283b5f2d88d1b76ed9356",