Series style guide
One acting system.
Two perspectives.
Editorial and visual standards for both Humaneness systems, the four taxonomies and all reference appendices
A quiet, readable reference series. Explain the idea first, show the relation, then preserve the full technical detail.
AUTHOR
Script Analysis System: turn a script into Character Makeup, scene obligations and beats with nested Experience Chunks.
PERFORM
Generate an audio or audiovisual performance from the authored character, scene and beat instructions.
OBSERVE
Performance Annotation: describe the available evidence and evaluate it under declared conditions.
01 / Editorial system
Understanding before lookup
Every volume must explain its purpose in the first sentences. Script Analysis designs virtual actors from source material. Performance Annotation describes and evaluates real-world, staged-reference and generated recordings. A catalogue page must explain its codes locally.
Three kinds of statement
| Kind | Write it as | Keep distinct from |
|---|---|---|
| Authored circumstance | “The script establishes fear; the character chooses reassurance.” | An inference about a real performer’s private state. |
| Observed evidence | “The voice remains steady; a pause precedes the answer.” | The emotion or mechanism that might explain it. |
| Interpretation / response | “The viewer reads restraint, with moderate confidence.” | An objective trait or an empirical validation result. |
A single shared authoring model
Source text → Character Makeup → scene-level Dramatic Obligations → Acting Beats → generated performance. Each beat contains outer dialogue, action or silence and exactly one nested Experience Chunk. The chunk specifies the fictional character’s attention, sensations, memories, associations, emotions and competing impulses; it does not claim that an AI system has subjective experience. The Emotional Obligation is one of the seven scene obligations, not a replacement for them.
Entry grammar
Put the human title first in the visual hierarchy, with a separate stable identifier. Follow it with the definition or premise. Give labelled fields for circumstance, suggested cues, observation, distinctions, starting axes and provenance as applicable. Give a plain-language meaning beside code references within each record. Repeat the dimension name in continued scale-table headers. Preserve exact identifiers and technical values; a dictionary at the front is not sufficient by itself.
Preserve the evidence
Keep all records, scale anchors, categories, questions, examples, source IDs and citations. Appendix A’s inherited definitions, anchors, “What to look for” and “Do not confuse with” are verbatim apart from whitespace. Add explanations outside those source fields. Keep the historical biological claims visibly subject to the interpretive corrections.
Long Morris entries are already abbreviated in the supplied reference. Mark these as source excerpts; never invent the missing endings or imply that the unavailable JSON companion is included. Treat absent referenced files as provenance records, not working download links.
Quiet provenance
State the framework name and version once at the opening. Use plain names in running headers and section titles. Keep source editions, historical release notes and exact file identifiers in the source register, rather than repeating them throughout the reading path.
Common structure
Cover with purpose and reading path → concise contents with page numbers → how to read this volume → complete content → source or editorial note where needed. Preserve the fourteen main-section numbers and appendix letters so inherited cross-references still work.
02 / Visual system
Calm pages, clear hierarchy
| Element | Standard |
|---|---|
| Page | A4 portrait; 19 mm top and side margins; 18 mm bottom margin. A single primary reading column. The four detailed Script Analysis System illustrations use dedicated A3 landscape plates so their labels remain readable. |
| Type | DejaVu Serif for display headings; DejaVu Sans for text; DejaVu Sans Mono for identifiers and code. Embedded fonts throughout. |
| Sizes | Cover 37 pt; chapter 23 pt; section 14 pt; entry 11 pt; prose 10.3 pt / 1.48; tables 9.1 pt / 1.43; metadata 8.6 pt. Do not shrink prose to fit a page. |
| Colour | Ink #192B40; teal #087E86; muted text #536775; pale teal #EFF5F5; warm note #FAF2E6; warm accent #BC633B. Meaning is also expressed in text. |
| Spacing | Regular 2–6 mm spacing between related blocks. Thin rules separate records. Avoid thick boxes around every entry and avoid artificially stretched pages. |
| Tables | Dark header, repeated on continuation pages; light alternating rows; top-aligned cells. Split long tables by rows, never reduce type to force a fit. |
| Navigation | Series name and volume in running headers; a volume-specific reading key and page number in footers; PDF bookmarks; linked contents; human-readable titles beside codes. |
Pagination rules
Keep headings with their opening text. Keep short records together; allow long records and scales to flow naturally, preserving row integrity. Keep a scale definition with the first anchor; avoid an entire scale being pushed to a fresh page. Start major chapters deliberately, but let catalogue families flow. Covers use their space to orient the reader.
Diagrams
Use vector diagrams for the shared system, evidence layers and the beat timeline. Each has one clear message, labels large enough to read, and a caption. Directional arrows indicate a workflow or an authored instruction, never proof of a hidden mental state.
03 / Production and review
Readable and complete
Deliver separate PDFs for the system overview, Script Analysis, Performance Annotation, all four taxonomies, Appendices A–J and this Style Guide. Keep editable HTML and the shared stylesheet with a reproducible build script.
- Compare source and output record counts, identifiers and scale anchors. Check supplementary material as well as the principal inventory.
- Extract text from every PDF. Check missing characters, literal markup, broken code, accidental duplication and clipped or out-of-page text.
- Inspect rendered pages from every volume, including opening pages, representative dense pages and the ending. Investigate sparse interior pages and unusually large gaps.
- Check bookmarks, contents page references, available local links and named external references. Identify which primary sources were inspected and pinned; distinguish those checks from inherited citations and from empirical validation.
- Record source limitations and any editorial amendments transparently. A more readable edition does not change the validation status of the integrated research framework.
Names and roles
Humaneness PerformanceNet is the umbrella. Humaneness Script Analysis System prepares fictional character and performance inputs from text. Humaneness Performance Annotation System encodes observed scenes and separates description, interpretation and evaluation. PerformanceNet Taxonomy, VoiceNet Taxonomy, EmoNet Taxonomy and PerformanceNet Situation Taxonomy supply complementary vocabularies. Use full system names at first mention; avoid using the taxonomy name for the whole annotation workflow.
Case catalogs are reference points, not an exhaustive Cartesian product. Preserve the source of each label, unknown values, local scale ranges and the distinction between proposed target coverage and measured data coverage. Reward models and omni-model representations are downstream uses; the taxonomies themselves are neither trained models nor validated quality scores.