Source: https://guthlabs.ai/docs/instruments/bitwise-operations-calculator/implementation/

instrument implementation / implementation-contract

# Bitwise Operations Calculator implementation

A source-bound implementation contract for Bitwise Operations Calculator; deployment and executable qualification remain separate.

Status: **VERIFIED_CLEAN**Lifecycle: **implementation-contract**

## Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

**Record owner**: Guth Instruments

**Lifecycle**: verified-clean

**Evidence ID**: t2-028

**Effect**: Computation or source lookup only

## Input and validation requirements

A zero-bit rotate produces an undefined negative shift count and has no valid result, so the calculator must reject it. The rotate operation also has a left-versus-right direction ambiguity unless the supplied formula and n-bit masking convention are enforced.

## Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

## Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

````
{
  "inputs": {
    "operation": "AND",
    "x": 172,
    "y": 102,
    "bit_width": 8
  },
  "expected_outputs": {
    "result_bin": "00100100",
    "result_hex": "0x24",
    "result_dec": 36
  },
  "working": "172 = 10101100₂ and 102 = 01100110₂. Bit by bit: 1&0=0, 0&1=0, 1&1=1, 0&0=0, 1&0=0, 1&1=1, 0&1=0, 0&0=0. Therefore 10101100₂ AND 01100110₂ = 00100100₂ = 0x24 = 36."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/bitwise-operations-calculator/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/bitwise-operations-calculator/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/bitwise-operations-calculator/qualification/>)

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `VERIFIED_LEDGER.json`

- `evidence-tranche2/tranche2-results.json`