# Engineering Drawing — style guide for coding agents

> Generated from the Aesthetary record for **Engineering Drawing**.
> Research: **Partly sourced** · Build guidance: recorded in 7 of 8 research dimensions.
> 14 sources attached.

## How to use this

Paste this file into your agent as context before asking it to design or build something in this visual language. It states what is established, what is our interpretation, and what nobody has established. Treat all three differently.

**The most important section is "Not researched yet".** Its purpose is to stop you and your agent inventing rules that sound right and are not recorded anywhere.

## What this language is

**Defining:** Multiple projected views, part numbering, coded line weights, title block

**Recognise it by:** Multiple views projected by a declared method, line types in a fixed width series, parts keyed by reference numbers, and a title block; in assembly and maintenance documentation, exploded views pull parts apart along shared axes. The isometric emphasis and the single orange accent are Aesthetary's reading. Blueprint is one reproduction of such a drawing, not its parent.

**Family:** Technical & Documentary
**Era:** contemporary
**Native medium:** print, software

**Scope:** Engineering drawing is a standards-governed technical notation. Aesthetary's register borrows its meaningful line types, orthographic discipline and part-numbered exploded views; the isometric emphasis and single orange accent are our reading.

## What it is arguing

A drawing is read by someone who was not there when it was made. Projected views, coded line widths, numbered parts and a title block let that reader recover the object exactly; where the drawing documents an assembly, pulling the parts apart along their axes shows relationship and order as well.

**It refuses:** Refuses any part shown without an identifier.

## What it is not

Commonly confused with these. Getting the difference right matters more than getting the surface right:

- Blueprint

## Established rules

Grouped by what kind of claim each is. A requirement of the language and our own interpretation are not interchangeable.

**How to read each rule.** Every rule states two separate things, and neither stands in for the other:

- **Kind of claim** (the heading): From our catalogue entry · disputed · From our catalogue entry · Documented · Source attached · Our reading · Documented · Source attached.
- **Evidence** (how it is established): Graded by our research brief · No source attached (`DOCUMENTED`) · From our catalogue entry (`SUPPORTED`) · Our reading (`CURATORIAL`) · Not researched yet (`UNKNOWN`) · No grade recorded (no grade in the record). Where a claim has its own canonical label, the Evidence line gives that label instead of the grade.
- **Product area**: which of the twelve areas the rule belongs to (Layout, Typography, Color, Imagery, Surface, Interface, Motion, Motif, Technique, Form, Hierarchy, Density), mapped from its raw area label in bold. "Context" means the rule is about the Aesthetic (its name, origin, lineage) rather than a part of the design. "Not mapped" means the raw area has no single area yet.
- The code in brackets is the `grade` field at `implementationConstraints.tokenRules.value.rules[].provenance.grade` in https://aesthetary.com/data/engineering-drawing.json. "From our catalogue entry" means: Stated in Aesthetary’s existing catalogue entry. An outside source is named only where one is linked to the claim.

### From our catalogue entry · disputed

_Carried over from Aesthetary's original catalogue entry. The reasoning behind it was never recorded._

- **layout** — Composition: isometric, exploded along axes.
  - Kind of claim: From our catalogue entry · disputed · Evidence: From our catalogue entry · disputed · Product area: Layout

### From our catalogue entry

_Carried over from Aesthetary's original catalogue entry. The reasoning behind it was never recorded._

- **hierarchy** — Hierarchy: part number + orange accent.
  - Kind of claim: From our catalogue entry · Evidence: From our catalogue entry · Product area: Hierarchy
- **color** — The single orange accent is a count constraint. A second accent breaks the "marks what matters" logic.
  - Kind of claim: From our catalogue entry · Evidence: From our catalogue entry · Product area: Color
- **imagery** — Imagery: isometric technical illustration.
  - Kind of claim: From our catalogue entry · Evidence: From our catalogue entry · Product area: Imagery

### Documented · Source attached

- **line** — Line type and weight together encode meaning: visible edges thick and continuous, hidden edges thin and dashed, centrelines thin chain. A line whose type carries no meaning is decoration and does not belong.
  - Kind of claim: Documented · Source attached · Evidence: Documented · Source attached · Product area: Imagery

### Our reading

- **motion** — Unusually well-founded: the register's own logic is assembly and disassembly, so parts separating and returning along their construction axes is native motion rather than imported web convention.
  - Kind of claim: Our reading · Evidence: Our reading · Product area: Motion

## Found in research

What research established from sources Aesthetary opened and checked. Each line names its area, how it is known, and where it is scoped. "Seen in the work" means the source documents particular works or products rather than the Aesthetic as a whole.

- **Typography** — Lettering practice is itself standardised (ASME Y14.2; ISO 3098), with nominal size defined by capital height.
  - Evidence: Documented · Source attached · Claim: `kcc:typography-1`
- **Typography** — Working-drawing lettering is a rapid single-stroke letter, vertical or inclined (1911 manual), with titles in single-stroke capitals; Wikipedia describes a Gothic sans-serif formed by short strokes, with lower case rare on machine drawings.
  - Evidence: Documented · Source attached · Claim: `kcc:typography-2` · Covers French 1911 manual; Wikipedia for current practice.
- **Typography** — ISO 3098 permits vertical or right-inclined (75 degree) lettering; a 1911 manual adds that one title must never mix the two.
  - Evidence: Documented · Source attached · Claim: `kcc:typography-3`
- **Typography** — Lettering must survive reproduction (diazo, microfilm, telefax).
  - Evidence: Documented · Source attached · Claim: `kcc:typography-4` · Covers ISO 3098-0.
- **Typography** — A 1911 manual condemned ruled geometric or block letters; ISO 3098 (1997) lists templates and manual lettering instruments among lettering techniques.
  - Evidence: Documented · Source attached · Claim: `kcc:typography-5` · Covers 1911 versus 1997.
- **Typography** — Wikipedia says many drawings have switched to Arial.
  - Evidence: Documented · Source attached · Claim: `kcc:typography-6` · Covers encyclopedic claim, unconfirmed elsewhere.
- **Surface** — Until the 1970s all engineering drawing was done manually in pencil and pen on paper or other substrates such as vellum and mylar; today most is done with CAD.
  - Evidence: Documented · Source attached · Claim: `kcc:surface-1`
- **Surface** — Tracing cloth was a starched, calendered cotton or linen, glossy on one side; draftsmen preferred the dull side because it took pencil.
  - Evidence: Documented · Source attached · Claim: `kcc:surface-2` · Covers 19th to mid-20th century.
- **Surface** — Drafting cloth gave way to acetate and polyester film by the mid-20th century.
  - Evidence: Documented · Source attached · Claim: `kcc:surface-3`
- **Interface** — Every drawing has a title block, placed bottom right on A0 to A3 sheets.
  - Evidence: Documented · Source attached · Claim: `kcc:interface-1` · Covers ISO 5457, with 1911 practice.
- **Interface** — The drawing space is bounded by a 0.7 mm continuous frame, with a margin that can be used for filing.
  - Evidence: Documented · Source attached · Claim: `kcc:interface-2` · Covers ISO 5457.
- **Interface** — ISO 7200 specifies the data fields used in title blocks, and advises avoiding the letters I and O because they are confused with 1 and 0.
  - Evidence: Documented · Source attached · Claim: `kcc:interface-3` · Covers ISO 7200.
- **Interface** — Manual practice laid out a bordered sheet and blocked out the title space before drawing, and repeated the filing number upside down in a corner for drawer retrieval.
  - Evidence: Documented · Source attached · Claim: `kcc:interface-4` · Covers French 1911.
- **Motion** — The exploded view shows the order of assembly or disassembly statically, by separating parts.
  - Evidence: Documented · Source attached · Claim: `kcc:motion-1` · Covers static drawings, including patent practice.
- **Motion** — SolidWorks can animate exploded views, and its Reciprocate option plays explosion and collapse forward and back.
  - Evidence: Documented · Source attached · Claim: `kcc:motion-2` · Covers contemporary CAD (SolidWorks) only.
- **Motif** — Part references are preferably numerals only, either encircled in same-diameter narrow-line circles or set in larger characters (e.g. twice dimension height), joined by leader lines that must not intersect.
  - Evidence: Documented · Source attached · Claim: `kcc:motif-1` · Covers ISO 6433.
- **Motif** — Part references sit outside the part outlines and are aligned in rows or columns.
  - Evidence: Documented · Source attached · Claim: `kcc:motif-2`
- **Motif** — Section lines are commonly called cross-hatching.
  - Evidence: Documented · Source attached · Claim: `kcc:motif-3`
- **Motif** — The sheet carries a grid reference border and centring marks for reproduction.
  - Evidence: Documented · Source attached · Claim: `kcc:motif-4` · Covers ISO 5457.
- **Form** — The drawing sits on flat sheets of standard size with a frame and filing margin, and represents 3D objects through several 2D views.
  - Evidence: Documented · Source attached · Claim: `kcc:form-1`

## Positions by area

The overall position recorded for each area. "No overall position recorded" means rules exist for the area but no position above them; the rules still apply. It is not the same as "Not established", which means nobody has researched the area.

- **Layout** — Specified
- **Typography** — Specified
- **Color** — Specified
- **Imagery** — Specified
- **Surface** — Left open
- **Interface** — Specified
- **Motion** — Specified
- **Motif** — Specified
- **Form** — Outside this language. The area does not apply; this is not a gap in the research.

## Design grammar — web primitives

A starting grammar for a website in Engineering Drawing: a framed white sheet with a title block, ink in one fixed series of line widths, every part keyed by a number, and one orange accent, which is our reading.

Three kinds of line: **On the record** names a rule this record holds (its wording is under Established rules) and states what it becomes on the web. **Web translation** is Aesthetary's choice for the web, derived from the rules it cites; change it if you have a reason, keep the cited rule. **Not specified by the source** means the research reached this but the sources say nothing about it; **Not researched yet** means the research has not reached it yet. Either way, follow the instruction and do not invent a rule. Structured version: `designGrammar` in data/engineering-drawing.json.

### Colour

| Role | Value | Contrast | Use | Kind |
| --- | --- | --- | --- | --- |
| sheet | `#FFFFFF` | — | The drawing sheet: the page ground. | Web translation |
| ink | `#22262B` | 15.2:1 | Every line and all lettering. | Web translation |
| ink-2 | `#5C636B` | 6.1:1 | Secondary lettering, centrelines, field names. | Web translation |
| rule | `#A9B0B8` | — | Narrow rules in tables and the sheet trim. Never text. | Web translation |
| accent | `#E8641B` | 3.3:1 (fill and line only) | The one accent: what matters, once. | On the record |
| accent-text | `#B8480C` | 5.3:1 | The accent when it has to be lettering. | Web translation |

- **On the record · From our catalogue entry** · `token_rule:color-5` → Use one accent colour and only one; a second accent breaks its "marks what matters" logic.
- **Web translation** — Draw in dark ink on a white sheet. _Why:_ Engineering drawings are now printed black or multicolour on white; a cyanotype ground is Blueprint, one reproduction of the drawing. (`claim:kcc:boundary-1`)
- **Web translation** — Letter the accent in the darker #B8480C; keep #E8641B for fills and lines. _Why:_ The orange fails text contrast on white (3.3:1); the one accent stays one hue. (`token_rule:color-5`)

### Typography

Family: a plain sans (the record declares typography free; IBM Plex is the room's choice). Stack: `"PlexSansX", "IBM Plex Sans", "Helvetica Neue", Arial, sans-serif`

| Role | Size | Weight | Line height | Case | Tracking | Measure | Setting | Use |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| title | clamp(2.375rem, 4.4vw, 4.25rem) | 300 | 1 | not specified | not specified | — | — | The drawing's title, once. |
| heading | clamp(1.375rem, 2.6vw, 1.875rem) | 500 | 1.2 | not specified | not specified | — | — | Section titles. |
| body | 1rem | 400 | 1.6 | not specified | not specified | 68ch | — | Notes and running text. |
| label | 0.75rem | 500 | 1.4 | uppercase | not specified | — | mono | Field names, part numbers, grid references. |

- **On the record · Documented** · `claim:kcc:typography-2` → Letter in a plain sans formed by single strokes; titles in capitals, lower case rare on the drawing itself.
- **On the record · Documented** · `claim:kcc:typography-3` → Set lettering vertical or inclined at 75 degrees, and never mix the two in one title.
- **Web translation** — Size type by its capital height and keep to few sizes. _Why:_ The standard defines nominal lettering size by capital height. (`claim:kcc:typography-1`)
- **Web translation** — Keep lettering fit to copy: no hairline strokes, no text in the pale rule grey. _Why:_ Lettering must survive reproduction (diazo, microfilm, telefax); a screenshot or a print is today's copy. (`claim:kcc:typography-4`)
- **Web translation** — Any plain sans will do; IBM Plex is this room's choice, not the language's. _Why:_ The record declares typography a freedom, and many drawings have switched to Arial. (`claim:freedom-typography`, `claim:kcc:typography-6`)

### Grid and layout

The page is a drawing sheet, not a column grid: a continuous frame with a wider filing margin on the left, grid references and centring marks on the border, the object shown in several views, and the title block bottom right.

Tokens: frame `2px` · filing-margin `clamp(1.25rem, 4vw, 2.5rem)` · sheet-margin `clamp(0.75rem, 2vw, 1.25rem)`

- **On the record · Documented** · `claim:kcc:interface-2` → Bound the drawing space with a continuous frame, with a margin that can be used for filing.
- **On the record · Documented** · `claim:kcc:interface-1` → Put the title block bottom right.
- **On the record · Documented** · `claim:kcc:motif-4` → Carry a grid reference border and centring marks on the sheet.
- **On the record · Documented / Our reading** · `claim:kcc:definition`, `claim:dcc:ed-r2` → Show the object in several views projected by one declared method, first angle or third; mixing them on one sheet is an error.
- **Web translation** — On a phone the title block closes the page rather than sitting in a corner. _Why:_ The record places it bottom right on A0 to A3 sheets; a phone is not a sheet, so the corner becomes the end. (`claim:kcc:interface-1`)

### Shape and geometry

Tokens: line-extra `4px` · line-wide `2px` · line-narrow `1px` · radius `0` · balloon `26px`

- **On the record · Documented · Source attached** · `token_rule:ed-r1` → Give each line a meaning by type and width: visible edges wide and continuous, hidden edges narrow and dashed, centrelines narrow chain.
- **Web translation** — Take every width from one series in the ratio 4:2:1 (4px, 2px, 1px here); there is no hairline. _Why:_ Line widths in a fixed 4:2:1 ratio are part of the record's definition; screen pixels keep the ratio. (`claim:kcc:definition`)
- **Web translation** — Keep corners square; the one round form is the part reference. _Why:_ Part references are encircled numerals; the record names no other rounded form. (`claim:kcc:motif-1`)

### Imagery

- **On the record · Documented** · `claim:kcc:motion-1` → In assembly documentation, separate the parts to show the order of assembly or disassembly.
- **Web translation** — Draw the exploded view in isometric, parts pulled apart along a shared axis. _Why:_ Isometric is the record's emphasis, and its reading, carried by its imagery and composition rules. (`token_rule:imagery-7`, `token_rule:layout-3`)
- **On the record · Our reading** · `claim:failure-5` → Do not draw in perspective.
- **Not specified by the source** — The sources do not specify photography. _Instead:_ Show objects as drawings. If a photograph is needed, keep it outside the sheet and do not call it part of the language.

### Title block

Every drawing identifies itself in one ruled block: owner, title, identification number, revision, sheet. On a page it holds the page's own identity, and only real metadata.

Tokens: tb-border `2px` · tb-rule `1px`

- **On the record · Documented** · `claim:kcc:interface-1` → Give every sheet a title block.
- **On the record · Documented** · `claim:kcc:interface-3` → Hold the standard's fields (owner, title, identification number, revision); avoid I and O in identifiers.
- **Web translation** — Fill it with real metadata only: an empty or decorative title block is not one. _Why:_ The title block is where the drawing identifies itself; the record refuses parts without identifiers. (`claim:kcc:interface-3`, `claim:idr:intent-negation`)

### Components

Anatomy, tokens and states below are Web translation: Aesthetary's specification for the screen. Each value line after them says whether it restates a rule this record holds.

#### Button

A drawn box: a wide ink line on the white sheet, the label lettered in mono; pressed, it fills with ink.

- Anatomy: 2px ink outline (the wide line); label in the mono face; square corners; no fill until interaction
- Tokens: border `2px solid #22262B` · background `#FFFFFF` · hover `#22262B fill, white label` · radius `0` · minHeight `44px`
- State, default: White field, wide ink outline.
- State, hover: Ink fill, white label. The swap is instant.
- State, focus: 2px ink outline 3px outside the box.
- State, active: Ink fill.
- State, disabled: Narrow (1px) dashed outline, the hidden-edge line; label in the secondary grey.
- Accessibility: Ink on white at 15.2:1; the inverted state keeps the same pair.
- Accessibility: At least 44px tall.
- Accessibility: Disabled is said in words as well as by the dashed line.
- **Web translation** — Draw the button as an outline in the wide line, square, with a mono label. _Why:_ Line type and width carry meaning; a control is a visible edge, drawn wide and continuous. (`token_rule:ed-r1`, `claim:kcc:definition`)
- **Web translation** — Show a disabled control with the narrow dashed line. _Why:_ Hidden edges are thin and dashed; an unavailable control is the one that is not there to use. (`token_rule:ed-r1`)

#### Card

A part on the sheet: a framed box keyed by an encircled reference numeral that sits outside it, on a leader.

- Anatomy: 2px ink frame; encircled numeral outside the frame, joined by a 1px leader; title in the sans at 500; one line of text
- Tokens: border `2px solid #22262B` · balloon `26px circle, 1px line` · leader `1px solid #22262B` · background `#FFFFFF`
- State, default: Ink frame, reference numeral in the margin.
- State, hover: Title underlined, 2px.
- State, focus: 2px outline outside the frame.
- State, current: The numeral's circle in the one orange.
- Accessibility: The whole card is one link; the numeral is part of its name.
- Accessibility: Order in the DOM follows the numbers.
- **On the record · Documented** · `claim:kcc:motif-1` → Key every part with a reference numeral, encircled in a narrow line, on a leader that crosses no other leader.
- **On the record · Documented** · `claim:kcc:motif-2` → Set the references outside the part outlines, aligned in a row or column.
- **Web translation** — Give every card a number; an unnumbered card is an unidentified part. _Why:_ The record refuses any part shown without an identifier. (`claim:idr:intent-negation`)

#### Input

A title-block cell: a ruled box with its field name small above, in mono capitals, and the entry beneath.

- Anatomy: 1px rule around the cell; field name in mono capitals, 12px; entry in the sans, 16px; error as a lettered line below
- Tokens: border `1px solid #22262B` · label `12px mono, capitals` · height `3rem` · radius `0`
- State, default: Narrow rule, white field.
- State, focus: The rule widens to 2px, and an outline sits outside it.
- State, error: Message below in the accent text colour (5.3:1), beginning "Error:".
- State, disabled: Dashed narrow rule.
- Accessibility: The field name is a real label above the field.
- Accessibility: Errors are words, not colour alone.
- **Web translation** — Build fields like title-block cells: the field name above, small, the entry below. _Why:_ ISO 7200 defines the named data fields a title block holds; a form is a set of named fields. (`claim:kcc:interface-3`)
- **Web translation** — Leave I and O out of any identifier the page generates. _Why:_ ISO 7200 advises avoiding them because they are confused with 1 and 0. (`claim:kcc:interface-3`)

#### Navigation

The parts list: numbered rows, each an encircled reference beside its title, which is the page's table of contents.

- Anatomy: table rows ruled in the narrow line; encircled numeral in the first column; title as the link; current row keyed in the orange
- Tokens: rule `1px solid #A9B0B8` · balloon `26px circle, 1px line` · current `#E8641B circle, #B8480C numeral`
- State, default: Numbered rows on the sheet.
- State, hover: Title underlined, 2px.
- State, focus: 2px outline around the row's link.
- State, current: The numeral's circle in the one orange.
- Accessibility: A real list or table with links; the numerals are text.
- Accessibility: aria-current on the current row, not colour alone.
- Accessibility: Each row at least 44px tall.
- **Web translation** — Number the navigation like a parts list, each item beside its reference numeral. _Why:_ Part references are numerals keyed to a list, and the record ranks by part number. (`claim:kcc:motif-1`, `token_rule:hierarchy-13`)
- **Web translation** — Mark the current item with the one accent, and nothing else in the list. _Why:_ The single orange accent marks what matters; a second would break it. (`token_rule:color-5`)

### Motion

Durations, easing and the rest of this specification are Web translation: Aesthetary's choice for the screen.

- Durations: explode 900ms, fade 600ms, swap 0ms
- Easing: axis `cubic-bezier(.6, 0, .2, 1)`
- Transforms: translate along the part's own construction axis only; no rotation, scale or perspective
- Entrance: none: the sheet is there when the page opens
- Hover: instant fills and line-width changes, no transition
- Reduced motion: Parts jump to their positions; nothing travels.
- **On the record · Our reading** · `token_rule:motion-14` → Move parts only along their construction axes: apart, and back together.
- **Web translation** — Play explosion and collapse on request (a button), forward and back; never on a loop or on scroll. _Why:_ Contemporary CAD animates exploded views and plays explosion and collapse both ways; the drawing itself shows the order statically. (`claim:kcc:motion-2`, `claim:kcc:motion-1`)

### Deliberately not added

- **A typeface** (typography): The record declares typography free and documents lettering practice, not a face.
- **Density of views and part numbers** (gridLayout): Density is not specified by the source; explosion distance and part-number density are declared freedoms.
- **Photography, and the technique area** (imagery): Technique is not researched yet; nothing on the record admits or rules out photographs.
- **Screen components** (components): The record documents the sheet's own conventions (frame, title block, filing number), not screen controls. All four components are translations of the sheet, the line series and the part reference.
- **A screen texture for the sheet** (shapeGeometry): Surface is left open: the record documents paper, vellum, cloth and film, not a texture to imitate.

## Coverage — what has been looked at

One row per research dimension a research pass considered. "Not researched yet" (`UNKNOWN`) means exactly that; a dimension can carry an Aesthetary recommendation and still be unresearched, and those are different things.

| Research dimension | Evidence | Resolved by | Carries a rule |
| --- | --- | --- | --- |
| Composition | Specified · From our catalogue entry | follows the recorded claim | yes |
| Typography | Specified | Aesthetary decided | yes |
| Hierarchy | Specified · From our catalogue entry | follows the recorded claim | yes |
| Colour | Specified · From our catalogue entry | follows the recorded claim | yes |
| Density | Not specified by the source | Aesthetary decided | no |
| Imagery | Specified · From our catalogue entry | follows the recorded claim | yes |
| Form / motif / surface / technique | Does not apply: form · Specified: motif · Left open: surface · Not researched yet: technique | follows the recorded claim | yes |
| Motion | Specified | Aesthetary decided | yes |

Unresearched: Typography, Motion. Where a rule appears for one of these it is Aesthetary's implementation recommendation, not a property of the language, and its Evidence line above says so.

## Not researched yet

Nobody has established a position for this language on:

- Technique

**Do not fill these in.** An absent position is absent research, not permission and not a blank for you to complete. If the work needs a decision in one of these areas, make it on other grounds and do not attribute it to this language.

## Grade your own work

17 checks: 6 mechanically testable, 9 needing a person to look, 0 needing a source Aesthetary does not hold, 2 with no recorded position. 1 further research dimension produced no rule (Density). This rubric is silent on it. Scores do not add up. A failure against a required rule and a departure from something we invented are not the same result, and no total should let them cancel.

### Recognition — does this read as the intended Aesthetic?

- **[visual_human · recognition signature · Evidence: No grade recorded]** Strip every logo, word and borrowed image out of your work, then show it to someone who knows the collection. Do they land on this Aesthetic? The signature to hold is: Multiple views projected by a declared method, line types in a fixed width series, parts keyed by reference numbers, and a title block; in assembly and maintenance documentation, exploded views pull parts apart along shared axes. The isometric emphasis and the single orange accent are Aesthetary's reading. Blueprint is one reproduction of such a drawing, not its parent.
  - _If it fails:_ The work may be competent and still read as a different Aesthetic, or as none. Nothing below matters until this passes.

### Fidelity — are its defining rules present?

- **[unassessable · no recorded position · Evidence: Not researched yet (`UNKNOWN`)]** Nothing is recorded as a requirement of this Aesthetic. There is no rule here that your work must hold — which means nothing you do can fail this dimension, and nothing you do can satisfy it either. That is missing research, not freedom: our research brief does record failure modes to avoid, listed under avoidance below. They are recorded judgement, not requirements.
  - _If it fails:_ Not applicable. An empty dimension is an absence of research, never a pass and never a failure.

### Implementation — were those rules translated appropriately into this medium?

- **[visual_human · From our catalogue entry · disputed · Evidence: From our catalogue entry · disputed]** Your work may depart from this — but knowingly, not by accident. Composition: isometric, exploded along axes.
  - _If it fails:_ A defensible departure, and you should be able to say why you made it.
- **[visual_human · From our catalogue entry · Evidence: From our catalogue entry]** Your work may depart from this — but knowingly, not by accident. Hierarchy: part number + orange accent.
  - _If it fails:_ A defensible departure, and you should be able to say why you made it.
- **[visual_human · From our catalogue entry · Evidence: From our catalogue entry]** Your work may depart from this — but knowingly, not by accident. The single orange accent is a count constraint. A second accent breaks the "marks what matters" logic.
  - _If it fails:_ A defensible departure, and you should be able to say why you made it.
- **[visual_human · From our catalogue entry · Evidence: From our catalogue entry]** Your work may depart from this — but knowingly, not by accident. Imagery: isometric technical illustration.
  - _If it fails:_ A defensible departure, and you should be able to say why you made it.
- **[visual_human · Our reading · Evidence: Our reading]** Your work may depart from this — but knowingly, not by accident. Unusually well-founded: the register's own logic is assembly and disassembly, so parts separating and returning along their construction axes is native motion rather than imported web convention.
  - _If it fails:_ Nothing. No one has researched the dimension yet, and this is only what Aesthetary would do. Departing from it costs you nothing.
- **[visual_human · Documented · Source attached · Evidence: Documented · Source attached]** Your work may depart from this — but knowingly, not by accident. Line type and weight together encode meaning: visible edges thick and continuous, hidden edges thin and dashed, centrelines thin chain. A line whose type carries no meaning is decoration and does not belong.
  - _If it fails:_ A defensible departure, and you should be able to say why you made it.

### Avoidance — known failure modes, neighbour drift, cloning

- **[mechanical · recorded failure mode · Evidence: No grade recorded]** Check your work against this: No cyanotype ground.
  - _If it fails:_ A failure mode recorded in our research brief: recorded judgement about what weakens this Aesthetic, not a requirement of the language.
- **[mechanical · recorded failure mode · Evidence: No grade recorded]** Check your work against this: No unnumbered parts.
  - _If it fails:_ A failure mode recorded in our research brief: recorded judgement about what weakens this Aesthetic, not a requirement of the language.
- **[mechanical · recorded failure mode · Evidence: No grade recorded]** Check your work against this: No second accent colour.
  - _If it fails:_ A failure mode recorded in our research brief: recorded judgement about what weakens this Aesthetic, not a requirement of the language.
- **[mechanical · recorded failure mode · Evidence: No grade recorded]** Check your work against this: No perspective.
  - _If it fails:_ A failure mode recorded in our research brief: recorded judgement about what weakens this Aesthetic, not a requirement of the language.
- **[visual_human · recorded failure mode · Evidence: No grade recorded]** Have you made any of these changes? Each one moves the work into a neighbouring Aesthetic: Blueprint is not Engineering Drawing's parent, nor its child. A blueprint is a reproduction of an engineering drawing made by a contact print process, and engineering drawings are made to suit several copying processes (diazo, microfilm, telefax). The two share the drawing's conventions (projected views, title block, dimensions); Engineering Drawing is the drawing, Blueprint the cyanotype print of it. Against Isometric (a projection Module): a static isometric with no explosion axes is the Module; the exploded view is assembly documentation.
  - _If it fails:_ You have built the neighbour. That may be fine — but name which Aesthetic you are in.
- **[mechanical · declared closure · Evidence: No grade recorded]** Check your work against this: Not open: blue ground.
  - _If it fails:_ This one is closed, not open. The record says generation must not go here.
- **[mechanical · declared closure · Evidence: No grade recorded]** Check your work against this: Not open: a line width outside the drawing's fixed series.
  - _If it fails:_ This one is closed, not open. The record says generation must not go here.
- **[visual_human · neighbour drift · Evidence: No grade recorded]** Could your work be mistaken for Blueprint? That language is: Drafting conventions used as layout structure, not decoration
  - _If it fails:_ Not necessarily wrong, but you are closer to Blueprint than to this Aesthetic.

### Accessibility — the Aesthetic preserved without its inaccessible practice

- **[unassessable · no recorded position · Evidence: Not researched yet (`UNKNOWN`)]** Does this Aesthetic conflict with any usability floor? Nobody has recorded one for it.
  - _If it fails:_ Nothing — and that is the problem. An unrecorded conflict is not an absent one. Hold AA on reading matter and decide the rest on other grounds.

**Not covered at all:** Density: Not specified by the source. These research dimensions produced no rule, so there is no check. Treat them as unscored, never as passed and never as failed.

## Rules for the agent

1. Do not invent rules for any area listed under **Not researched yet**.
2. Do not treat an absent position as permission to do anything you like — say that the language has no position, and decide on other grounds.
3. Keep our interpretations separable from the language's own requirements. If asked to justify a choice, cite which kind of claim it came from.
4. If you need something this record does not contain, say so rather than producing a confident answer from the aesthetic's name.
5. When you self-score against "Grade your own work", score only checks marked `mechanical`. Declare `visual_human` and `evidence_dependent` checks unjudged rather than guessing, and never score an `unassessable` one.
6. Evidence "Not researched yet" (`UNKNOWN`) is never a failure. It means nobody researched the dimension, so departing from what is written there costs nothing and must not be reported as a defect. "No grade recorded" is not a grade either: do not treat it as our decision or as an outside source.
7. In **Design grammar**, a "Web translation" line is our choice for the web and may be changed with a reason; the rules it cites may not. Never present a translation as a property of the language.

## Provenance

- Record: `engineering-drawing` · status `needs_review` · research `partly_researched`
- Full structured record: https://aesthetary.com/data/engineering-drawing.json
- Human-readable record: https://aesthetary.com/a/engineering-drawing.html
- This file is a snapshot. The record may have changed since; check the page above.

_Aesthetary is an alpha. Where a page says nothing, nobody has done the work yet._