docs: llms.txt + sikkerhetskontakt til security@ (ORDRE 20260821T041218Z)
D2b: llms.txt i rota - H1, blockquote, EN startkommando byte-identisk med README-ens forste kodeblokk (verifisert med diff), Docs- og Optional-seksjoner med relative fillenker. Loser README-ens tre konkurrerende startverb ved a velge den dokumenterte veien. Minimal med vilje: llms.txt er en konvensjon, ikke en ratifisert standard. Begrunnes IKKE med crawlere - leseren er en KI-agent som allerede star i repoet. D6: SECURITY.md sin kontaktadresse hello@ -> security@fromaitochitta.com. Kun sikkerhetskontakten; hello@ i CODE_OF_CONDUCT.md star urort (riktig for alt annet). shared/SECURITY.md er urort - shared/ er pull-only subtree fra commons og eies der. I samme okt (operator-ja 21.08): docs/extending.md sa "no bundled example ships a cost-baseline.json (checked)". Usant siden 09.08 - MALT: veglys-fv-soer og tunnel-hauglia shipper begge fila. Setningen peker na pa den shippede fila som formreferanse og gjengir ir.CostBaseline korrekt (project_id + items-map). llms.txt ligger utenfor _LIVE_DOCS-gaten (den skanner README.md + docs/**/*.md), verifisert i testfila - ingen ny doc-klassifisering kreves. Handover-gatens _REQUIRED_MEMBERS er en tilstedevaerelses-sjekk, ikke en uttommende liste. 874 passed / 5 skipped, uendret. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DA6HAF8HFQxGYC2h6ypRQe
This commit is contained in:
parent
9d149b3503
commit
0bc8dae5c0
3 changed files with 38 additions and 4 deletions
|
|
@ -74,9 +74,10 @@ layer does **not** produce: ingest materializes *source documents*, while the IR
|
|||
the *candidate measure*, and no connector can infer one from the other. A bundle may also ship an
|
||||
optional `cost-baseline.json`; without it the validator still runs, but unanchored to the
|
||||
project's real cost lines. Both are hand-authored today. For the IR projection the shape reference
|
||||
is `shared/examples/bygg-energi-mikro/validator-input.json`; **no bundled example ships a
|
||||
`cost-baseline.json`** (checked), so its shape — `{code: {quantity, unit_cost}}` — comes from
|
||||
`ir.CostBaseline` and the README. Writing them from ingested content is
|
||||
is `shared/examples/bygg-energi-mikro/validator-input.json`; for the cost baseline it is
|
||||
`shared/examples/veglys-fv-soer/cost-baseline.json` — **two bundled examples ship one** (that one
|
||||
and `tunnel-hauglia`, checked 2026-08-21), and its shape is `ir.CostBaseline`: a `project_id` plus
|
||||
an `items` map of `{code: {quantity, unit_cost}}`. Writing them from ingested content is
|
||||
unbuilt, and is not on the 90 %-principle side of the line: what candidate to propose is the
|
||||
agents' job, not the connector's.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue