Skip to content
Source
Sign inSign up
TanStack/db

docs(oracles): score oracle-first work and add declared reach #2233

MergedKyleAMathews(GitHub profile, opens in a new tab)merged 4 commits intomain fromrefs/pull/2233/headmerged by KyleAMathews(GitHub profile, opens in a new tab)

Showing 6 changed files with 52 additions and 1 deletion (loading 3).

x
0 of 6 viewed, 6 left
20 additions and 1 deletion.agents/skills/oracle-authoring/SKILL.mdModified
View file
@@ -13,6 +13,24 @@
grammar, or comparison that it uses. This includes a change made while you fix
a bug, fix a review finding, or evaluate review findings.
​
+Read [how oracle work is scored](../../../AGENTS.md#how-oracle-work-is-scored)
+first. Auditors check the order of your work and penalize shortcuts.
+​
+Work in this order when a production change is part of the task:
+​
+1. State the law and its authority.
+2. Extend the history grammar, driver, or observation until generated
+ histories reach the state where the law matters. Declare that state with
+ `createOracleReach` (ORC-015).
+3. Run the extended oracle on the unchanged production code and record the RED
+ failure.
+4. Change production, with the oracle running after each attempt.
+5. Record the GREEN result and a hostile mutant that fails.
+​
+Do not change production before step 3. If a model rule disagrees with
+production, find its authority before you edit either one. A rule that you
+change only so that it matches production output is model hacking.
+​
Read [the oracle guide](../../../docs/contributing/oracle-rubric.md),
[the glossary](../../../docs/contributing/glossary.md), and the relevant owner
and limits in [the coverage map](../../../docs/contributing/oracle-coverage.md).