- description
- d2spec's facts for the d3 skills — the names and values the skills leave as <placeholders>. Trial topic, cut from Skill:process; not a skill.
- tags
- #d3skill
- work
- razwip
- main
- main
- repo
- razie/diesel2
- repoSecret
- github-diesel2
- impl
- proto1
- implDir
- proto1/
- implDocs
- Proto1Impl, Proto1Code, Proto1Routes, Proto1Test
- designDocs
- Spec, SpecUi, Design, DesignRoutes, Testing
- testBasic
- npm test
- testFull
- npm run test:full
- testDeploy
- npm run test:deploy
- testGate
- npm run test:gate
- testLate
- npm run test:late
- testMessaging
- npm run test:messaging
- typecheck
- npm run check
- prodBox
- cloud4
- replicaBox
- cloud5
- conformance
- d2conf
- baseHost
- https://aiputty.com
- releaseWord
- run the full test and deploy
- project
- d2spec
d3-process: d2spec's facts¶‹ Previous
The frontmatter above is the whole of it: each key is a fact about d2spec, and the trial skills API (GET /api/v2/skills/d3) puts its value wherever a served skill line says <key> — <work> becomes razwip. Rules never live here: a rule belongs to a feature skill (d3-f-…) or to a role (d3-r-<role>, and d2spec's own d3-r-<role>-d2spec).
| key | what it is |
|---|---|
work |
the work branch every builder merges into |
main |
the released branch; it moves only at a release |
repo, repoSecret |
the GitHub repository and the vault secret that clones it |
impl, implDir, implDocs |
d2spec's one code implementation, its folder in the repo, and the topics its builders keep |
designDocs |
the design layers only the designer writes |
testBasic, testFull, testDeploy, testMessaging, typecheck |
the implementation's commands, run in implDir |
testGate, testLate |
the run before a release, and the run after its deploy (testFull is both) |
prodBox, replicaBox, conformance |
production, its replica, and the project the box suite runs against |
baseHost |
base d2, where inherited content is edited |
releaseWord |
what the Architect says to ask for a release |
Keys must not be a word the skills use as a blank to fill in — name, role, id, project, person, agent, topic, check, code, date and the like — or that blank would be filled with the fact.
Still in process until the trial is the default: everything else d2spec does its own way.