Cag Peptide Calculator Research Notes Collection

What the tool computes

The tool on this page performs one operation: it divides a stated mass by a stated volume and displays every step of the working, including the aliquot figures derived from the same division. Showing the working is the design principle, because a calculator that hides its steps asks for trust and one that shows them asks for a check.

The operation is the only part of the reconstitution chain that a remote reader can verify independently. Everything upstream, the mass on a label, the composition statement behind it, the certificate that names a method, is documentary work the tool cannot perform.

Nothing is stored or transmitted. The arithmetic runs locally in the browser, and the interface states this in plain language.

The tool's contract, stated once and repeated in the linked note: it computes figures, it verifies nothing about the inputs, and it excludes everything that would require compound-specific constants or a stated purpose.

Units and conversions

Published work reports concentration in mass per volume, most commonly milligrams per millilitre and micrograms per millilitre, which differ by a factor of one thousand. The tool displays the first and converts between the two explicitly rather than silently.

Molar concentration requires the molecular weight of the specific compound, and the tool refuses the conversion rather than approximating it with an invisible constant. A reader who needs molar figures supplies the weight and performs the conversion explicitly, which is the correct place for that assumption to live.

Unit discipline is the section's recurring theme: pack mass, concentration and administered levels are three different quantities from three different systems, and blurring them is the most common arithmetic error in the category.

The notebook's dose-structure records keep the systems in separate columns for exactly this reason, and the linked notes describe the separation in detail.

Reading certificate numbers alongside the arithmetic

A certificate supplies the figures the arithmetic consumes: the nominal mass, the lot, the method and the result. Reading the certificate before the arithmetic is the section's standard, because a correct division of a misread mass is a confident error.

The header of a real certificate names the compound, the lot, the method, the result, the date and the issuing laboratory. Cropping any of those fields is a choice, and the choice is informative regardless of intent.

The notebook records certificate artefacts as artefacts: which field is missing, what the document does not establish, and what a reader would need to close the gap. That is a more useful observation than a verdict about motives.

Where the arithmetic and the certificate disagree, the disagreement is the finding, and it is recorded with both sources dated.

Common arithmetic pitfalls with small figures

Small-mass entries produce concentrations where a misplaced decimal changes the result by an order of magnitude and leaves the final number looking plausible. Shown working is the only safeguard, which is why the tool displays every intermediate step.

The second pitfall is volume assumptions: a solvent statement that does not specify volume leaves the division undefined, and the notebook records such statements as gaps rather than assuming a default.

The third is reuse across revisions: pack figures change, and arithmetic performed on last quarter's mass is quietly wrong for this quarter's pack. Redoing the division with current figures takes seconds.

Each pitfall is documented with an example in the linked notes, and the examples are dated like every other record in the notebook.

Charts and tables in the literature

Published reporting tables are design artefacts: rows tied to models, columns tied to cohorts, headers carrying units. A chart copied without that grammar is a floating number set, and the section's chart note describes the anchoring method.

The anchor is three fields: publication, design and duration, recorded beside every copied table. A table without an anchor is not filed in the notebook, because it cannot be distinguished from an invented one.

Tables are revised across publication versions, so the version is part of the anchor. The notebook has recorded differing rows across versions of the same table.

The tool on this page does not host charts for personal application. It hosts arithmetic and the reading method, which is the scope the section maintains.

Limits of the tool

The tool's limits are stated as deliberately as its function: no storage, no transmission, no molar conversion, no handling guidance and no verification of inputs. Each limit exists because the alternative would import an invisible assumption.

The largest limit is the input boundary: figures come from composition statements and certificates, and checking those remains the reader's documentary work. The tool checks arithmetic; it cannot check provenance.

The limits are revisited when the section's scope changes, and any change will be described on the tool page rather than slipped into the interface.

A reader who wants a tool with a larger scope should expect that tool to state its assumptions explicitly; any calculator that hides them is asking for trust where a check belongs.

Worked examples in the section

The section's arithmetic notes carry worked examples kept deliberately generic: a mass, a volume, a division shown line by line. Generic examples age well, avoid anchoring to any pack, and can be re-done by any reader with a pencil.

Each example closes with the multiply-back check, where the computed concentration is multiplied by the volume to recover the stated mass. The check catches every decimal-error class the section's audits have reconstructed, at the cost of one line.

The examples' numbers are chosen to make the arithmetic legible rather than realistic, and the notes say so: realism belongs to the reader's own figures, and the example's job is to demonstrate the method, not to supply one.

Examples are dated like every record in the notebook, and when the method text changes, the affected examples are revised rather than left inconsistent with the method that cites them.

The multiply-back check

The multiply-back check deserves its own section because it is the highest-value habit in the section's material: one line of multiplication that recovers the stated mass from the computed concentration.

The check's power comes from direction reversal. Forward arithmetic repeats the reader's own path, including their own mistakes; the reverse path multiplies independent figures, and a mismatch localises the error to one line.

In the section's audit reconstructions, the check caught every error class inserted into the sample arithmetic, including the small-figure decimal errors that survive every visual plausibility test.

The check is taught on the calculator note, demonstrated in every worked example, and recommended to readers as the one habit worth carrying out of this section.

Interface decisions as scope decisions

The calculator's interface is documented as a set of scope decisions: three inputs, one division, no memory, no network calls, and a working display that shows every intermediate line.

Each decision excludes something a commercial tool would include, and the exclusions are stated with reasons: memory implies profiles, network calls imply transmission, and hidden steps imply trust where a check belongs.

The decisions are revisited at each audit cycle, and a change to any of them would be described on the tool page before it shipped, which is the same disclosure standard the About page promises for the notebook's commercial elements.

The documentation of interface decisions doubles as a reader's guide: a reader who has read the decisions knows exactly what the tool does, which is more than most tools in this category offer their users.

Maintaining the tool records

The tool's records follow the notebook's dated format: design decisions, audit findings and example revisions each carry dates, and older versions remain visible beside newer ones.

Records are re-checked at each audit cycle for consistency with the interface as actually deployed, because documentation that drifts from its tool is a quiet failure mode the section takes seriously.

Audit findings about the tool are filed in the same format as the section's other records: observation, date, and the limit of what the observation supports.

The maintenance standard is the same one the section teaches, applied to itself, and the symmetry is deliberate: a section about shown working should be able to show its own.

Arithmetic the section refuses to perform

A closing note records the arithmetic this section declines, and why: molar conversion without compound-specific constants, any conversion between pack systems and administered levels without a design context, and any figure whose inputs the reader cannot source to a composition statement or certificate.

The refusals are stated as scope decisions rather than limitations, because each one protects an assumption the reader should own explicitly instead of inheriting silently from a tool.

The refusal list is revisited at each audit cycle, and items leave the list only when the assumptions they guard can be made explicit in the interface.

The list's existence is the section's most concise statement of its philosophy: tools earn trust by showing their limits, and a tool without a stated refusal list has simply declined to publish its assumptions.

How the section's notes support the tool

The tool page and its two notes form a deliberately small loop: the tool computes, the calculator note states the contract, and the chart note teaches the reading method for the tables whose figures the arithmetic consumes.

The loop's smallness is a design choice: each page exists to support the others, and no page in the section introduces material the other two cannot verify or bound.

The section's cross-links run to Brands for the paperwork standard and to Research for the reporting grammars, which is where the tool's inputs and the charts' contexts respectively live.

Readers who want more tooling than the section offers are pointed at the method rather than at more features, on the argument that a second tool with hidden assumptions is a worse outcome than one shown-working tool plus a reading habit.

Units, rounding and record-keeping

Every arithmetic page in this collection follows three fixed conventions. First, concentrations are stated in mass per volume, never in activity units, so that a figure can always be re-derived from the vial description it came with. Second, rounding is shown at the step where it happens, not silently at the end, so a reader reproducing the arithmetic can see where trailing digits were dropped. Third, every worked example carries a date and a source-type label, because notation habits drift between textbooks and community write-ups.

The chart note and the calculator note are designed to be read together: the calculator note explains the arithmetic, and the chart note explains how published tables compress the same arithmetic into lookup rows, along with the reading errors that compression invites. Working through both takes most readers under twenty minutes and removes most of the confusion the archive receives questions about.

Units, rounding and record-keeping

Every arithmetic page in this collection follows three fixed conventions. First, concentrations are stated in mass per volume, never in activity units, so that a figure can always be re-derived from the vial description it came with. Second, rounding is shown at the step where it happens, not silently at the end, so a reader reproducing the arithmetic can see where trailing digits were dropped. Third, every worked example carries a date and a source-type label, because notation habits drift between textbooks and community write-ups.

The chart note and the calculator note are designed to be read together: the calculator note explains the arithmetic, and the chart note explains how published tables compress the same arithmetic into lookup rows, along with the reading errors that compression invites. Working through both takes most readers under twenty minutes and removes most of the confusion the archive receives questions about.