open-standards/joulespec/LICENSE
Transaction Science 5a7af57afb
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 7s
standards workspaces build + test / joulehook-rs (joulehook/joulehook-rs, joulehook-rs, linux) (pull_request) Successful in 45s
standards workspaces build + test / jouledesk-rs (jouledesk/jouledesk-rs, jouledesk-rs, macos) (pull_request) Successful in 59s
standards workspaces build + test / pool-rs (pool/pool-rs, pool-rs, linux) (pull_request) Successful in 1m5s
standards workspaces build + test / arl-rs (arl/arl-rs, arl-rs, linux) (pull_request) Successful in 1m16s
standards workspaces build + test / jcp-rs (jcp-conformance, jcp/jcp-rs, -p jcp-energy --features nvml, jcp-rs, linux) (pull_request) Successful in 1m19s
standards workspaces build + test / proof-rs (proof-conformance, proof/proof-rs, proof-rs, linux, true) (pull_request) Successful in 44s
standards workspaces build + test / joule-ui-rs (joule-ui/joule-ui-rs, joule-ui-rs, linux) (pull_request) Successful in 1m41s
standards workspaces build + test / sense-rs (sense/sense-rs, sense-rs, linux) (pull_request) Successful in 34s
standards workspaces build + test / joulespec-rs (true, joulespec/joulespec-rs, joulespec-rs, linux) (pull_request) Successful in 38s
standards workspaces build + test / sandbox-rs (sandbox-conformance, sandbox/sandbox-rs, -p sandbox-tee --features amd-kds,intel-pcs, sandbox-rs, linux) (pull_request) Successful in 1m9s
standards workspaces build + test / eoc-rs (eoc/eoc-rs, -p eoc-meter --features cuda, eoc-rs, linux) (pull_request) Successful in 2m24s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m48s
standards workspaces build + test / smart-byte-rs (smart-byte/smart-byte-rs, smart-byte-rs, linux) (pull_request) Successful in 2m11s
standards workspaces build + test / aac-rs (aac-conformance, aac/aac-rs, aac-rs, linux-arm64) (pull_request) Successful in 4m7s
standards workspaces build + test / jouleclaw-rs (-nodebug, jouleclaw/jouleclaw-rs, -p jouleclaw-energy --features rapl,nvml, jouleclaw-rs, linux-arm64, -C target-feature=+fp16) (pull_request) Successful in 4m10s
standards workspaces build + test / joulecontract-rs (joulecontract/joulecontract-rs, joulecontract-rs, linux-arm64, true) (pull_request) Successful in 1m6s
standards workspaces build + test / map-rs (map-conformance, map/map-rs, map-rs, linux-arm64) (pull_request) Successful in 1m9s
standards workspaces build + test / mesh-rs (mesh/mesh-rs, -p mesh-engine-gguf -p mesh-openai --features mesh-engine-gguf/gguf,mesh-openai/server, mesh-rs, linux-arm64) (pull_request) Successful in 1m4s
standards workspaces build + test / openpay (openpay, openpay, linux-arm64) (pull_request) Successful in 3m37s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 6m39s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 10m31s
joulespec: a standard for energy-accounted specification conformance
Specification-driven practice converged on prose an agent interprets and a
human reads. The difficulties catalogued wherever it is examined -- specs
drifting from the code they describe, generated artifacts trusted past their
evidence, no method for checking conformance, a review burden heavy enough
that practitioners report preferring to read the code -- are measurement
problems rather than methodology ones, and they persist for one reason: the
specification is a document. A clause cannot be addressed, so nothing binds
to it; conformance is a sentence in a review, so it cannot be graded or
capped; the cost of the ceremony is an anecdote, so the argument about
whether it earns its overhead has no units.

joulespec/1 leaves the prose alone and changes what the specification is.

Addressing (SPEC 1.2, 2.1). A clause carries a label AND an obligation: the
content address of its kind and text, with the label deliberately excluded.
Evidence binds to the obligation, so renaming a clause loses no evidence
while rewording one invalidates exactly that clause's evidence. Binding by
label inverts both halves -- it survives the edit that changed the
requirement and breaks on the edit that renamed it -- which is the mechanism
by which drift goes unobserved rather than a discipline failure.

This corrects our own prior art. joule-code-spec shipped the signed,
content-addressed clause and the citation binding a coding op to it, and its
citations bind by clause LABEL with a single notion of coverage: a clause is
covered when something claims it. That is the E0 rung here.

The ladder (SPEC 2.5, 2.6), ordered by one question -- how hard would it be
for this obligation to be violated without this evidence noticing?

  E0 cited        the implementer says so; where prevailing practice lands
  E1 reviewed     a second party read the artifact, once
  E2 exercised    a named check ran and passed -- and flatters: a test with
                  no assertion passes, as does one whose fixture never
                  reaches the condition the clause cares about
  E3 falsifiable  the same check is on record FAILING against a named
                  counter-artifact: the first rung where green means
                  something, and the cheapest strong one
  E4 proved       no input violates it, under a formalization cross-checked
                  by a key other than the prover's

A proof under a merely declared formalization grades E2, not E4: it is
machine-checked evidence that the something is this clause on the prover's
word. Demotion rather than refusal -- the proof is not fake. The crate never
formalizes a clause itself, and independence is computed from key
disjointness, never read from a producer's flag: a review signed by the
citing key is the citation again.

Evaluation (SPEC 3). A specification's grade is its WEAKEST owed obligation,
absent entirely when any has no surviving evidence; averaging would let nine
proved obligations conceal one nobody looked at. Non-goals are first-class
and excluded from the cap -- an unwitnessed non-goal is correct -- while
evidence that one WAS implemented is a flag that blocks conformance however
good the rest is. Nothing is dropped quietly: an unverifiable witness, one
naming another specification, and one naming an obligation the spec does not
state are each reported, that last being the normal aftermath of a rewording.
Ties break on address, so reordering the inputs cannot change the verdict.

Drift (SPEC 4) is a partition over addresses, not a warning: kept,
relabelled (editorial, no evidence lost), reworded (that clause's evidence
invalidated), added, removed -- from which the two sets a revision review
wants fall out. A freed label reused by a new clause is an addition, not a
rewording, because the old obligation still stands. The other direction needs
no diff: a witness is bound to the artifact state it observed, so evidence
from an earlier state is stale rather than counted.

Cost (SPEC 5). Witnesses and work each carry their joules, so the receipt
seals the specified share -- how much energy went into work citing no clause,
the measured form of agents producing features nobody requested -- and
microjoules per falsifiable obligation. That denominator is deliberately the
rung whose evidence can fail: a figure per ATTEMPTED obligation rewards
ceremony, and this family's other per-unit figures count accepted tokens and
verified proofs rather than attempts. Absent where nothing reaches the bar; a
cost per unit of nothing is not a small number.

Receipts (SPEC 6) are derived from the specification, artifact, witnesses and
work -- never from a verdict handed in. A verdict is an ordinary struct, and
an interface that signed one would let a producer construct the grade it
wanted. Sealed as joulespec/1 JCR-1 (canonical det-CBOR under COSE_Sign1,
Ed25519), byte-compatible with the family verifiers. The core admits no
nulls and several figures are legitimately absent, so those keys are OMITTED
rather than zeroed: a reader finding no grade knows none was established,
where one finding E0 would believe otherwise. Each receipt carries the
per-clause audit, because which obligation is the weak one is the actionable
fact and must be answerable from the receipt alone.

CI: joulespec-rs joins the standards matrix on `linux` with a new opt-in
`clippy: true` flag that gates the workspace at zero warnings on its own
runner. Deliberately not added to the macOS lint step -- that exists for code
only a macOS host can compile, and this workspace has no Apple anything. The
flag is per-entry rather than repo-wide because several workspaces are not at
zero yet, and a gate that fails on arrival teaches people to pass
--no-verify.

The modules cite their normative sections, so check-spec-refs binds the code
to the specification mechanically -- which this standard of all of them
should do.

cargo check/clippy/test --workspace --all-targets --locked: green, zero
warnings, on the M3 Ultra build host.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-11-01 08:04:52 -05:00

202 lines
11 KiB
Text

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.