Skip to content

armgit / hypit

Public Imported from GitHub
0

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

docs(skill): connect image direction and complex explainer lessons

kashorin345abba21a5b
diff --git a/examples/complex-explainer/README.md b/examples/complex-explainer/README.md
index ae413851..92a92db9 100644
--- a/examples/complex-explainer/README.md
+++ b/examples/complex-explainer/README.md
@@ -73,6 +73,7 @@ explains joining exported parts. The archive also includes `productions/explaine
| How does each coordinated scene behave? | [Web scenes](packages/web-scenes/README.md) |
| How do the presenter and opening graphics move? | [Opening system](packages/opening-system/README.md) |
| How are cue boundaries and one-line captions handled? | [Caption package](packages/single-line-captions/README.md) |
+| Where does the shared palette live without becoming another Track? | [Visual language](packages/visual-language/README.md) |
| Which existing material should a new Build use? | [Render Run](productions/explainer/runs/render.svrun) |
Generated and normalized Outputs remain in the entry Source where the Run can satisfy them explicitly.
@@ -90,7 +91,10 @@ Tracks. The scene's state is computed from frame time, making direct seeking and
possible. Script Moments locate spoken changes; authored durations shape how those changes unfold.
Read the [Treatment](productions/explainer/TREATMENT.md) and
-[craft notes](productions/explainer/CRAFT-NOTES.md) for the practical reasoning. Components use public
+[craft notes](productions/explainer/CRAFT-NOTES.md) for the practical reasoning: recovering behavior
+beyond a list of objects, the style change, scene boundaries, semantic events, framing and review.
+The [presenter-led visual explainer playbook](https://github.com/hypit-ai/hypit/blob/main/skills/hypit/references/playbooks/formats/presenter-led-explainer.md)
+draws out the whole-work relationship for other productions. Components use public
Author Package and Companion interfaces; Studio and Core contain no dispatch for this example.
## Materials and editorial copy
diff --git a/examples/complex-explainer/packages/visual-language/README.md b/examples/complex-explainer/packages/visual-language/README.md
new file mode 100644
index 00000000..850a573e
--- /dev/null
+++ b/examples/complex-explainer/packages/visual-language/README.md
@@ -0,0 +1,16 @@
+# Shared visual language
+
+An ordinary JavaScript dependency containing this production's named palette and its CSS-variable
+representation. `palette` supplies the color values; `paletteCss` supplies a `:scope` rule with the
+same names. Scene packages import the representation their renderer needs.
+
+```js
+import { palette, paletteCss } from "@explainer/visual-language";
+```
+
+This package declares no Hypit Module, Surface, Track or Companion. Sharing a design decision does
+not by itself create a visible component. Scenes still own their geometry, typography, depth and
+motion; changing this palette alone does not implement a complete change of visual style.
+
+Keep the colors that serve this film, or revise them as one shared design decision when adapting it.
+They are not defaults prescribed for other productions.
diff --git a/examples/complex-explainer/productions/explainer/CRAFT-NOTES.md b/examples/complex-explainer/productions/explainer/CRAFT-NOTES.md
index 22373fb3..99c34f38 100644
--- a/examples/complex-explainer/productions/explainer/CRAFT-NOTES.md
+++ b/examples/complex-explainer/productions/explainer/CRAFT-NOTES.md
@@ -1,29 +1,119 @@
# Lessons from the explainer
+Read alongside the [finished work and project guide](../../README.md) and [Treatment](TREATMENT.md).
+This is a retrospective of the decisions behind one complex spoken explainer. The useful inheritance
+is how a visual problem was understood and given an owner; its pink treatment, scene inventory and
+production settings are choices for this work.
+
+## Understand behavior beyond the inventory
+
+Early descriptions could identify a presenter, cards, diagrams and a countdown without explaining
+what made them effective. A card that first establishes an alternative and then remains below a
+demonstration is doing a different job from a fresh title card at every sentence. A drag attempt
+needs contact, displacement and rejection to communicate failure; naming the objects does not
+specify that experience.
+
+Looking more closely at the reference's transitions changed the reading of its larger structure.
+Reading the speech alongside those frames made it possible to name what each change answered.
+The lesson is to move continuously between the argument and its realization, examining the interval
+that resolves the current question and explaining the growing understanding to the user. The public
+example retains the target design and sources; it does not distribute the reference creator's footage
+or the private review conversation.
+
## Organize responsibility before exposing controls
A component is a useful owner of related behavior. Parameterization is a separate choice about what the author should vary; cross-project reuse is another choice about a demonstrated future need. The editor demonstration is one coherent scene because its folder, pointer and timeline respond to each other. Its exact pixel dimensions can remain internal. The background, Caption and presenter have independent reasons to change and deserve independent ownership.
+The initial implementation accumulated large scene strings and repeated decisions, making revisions
+hard to locate. The useful cleanup separated scene content, styles and frame evaluation into ordinary
+modules, with shared mechanics kept in shared dependencies. It did not turn every illustrated button
+into an independent Track or expose an entire editor's geometry as author controls. A file boundary,
+a package boundary and a visible Track can serve different purposes.
+
+See the [scene map](../../packages/web-scenes/README.md). Each scene can keep a designed internal
+layout while accepting the material and semantic events the work really changes. The separate
+[visual-language package](../../packages/visual-language/README.md) shares palette values without
+declaring any visible contribution.
+
## Give changes meaningful event names
The Script identifies the phrase that motivates a change. A scene receives events such as “install”, “examples” or “guess”; its code turns those events into local motion. Direct time and frame counts remain useful for transition duration, silent endings and fast montages. This lets timing move with accepted performance without rewriting every animation timestamp.
+For one concrete trace, [Script](authors/script.svml) places `road-fail` at the spoken claim that motion
+is difficult. [Main Source](authors/main.svml) connects that meaning to the editor scene:
+
+```svml
+<webscene:Beat name="fail" at={copy.story.moment.road-fail}/>
+```
+
+The scene projects the event to a frame. Its
+[animation](../../packages/web-scenes/src/scenes/editor-route/animation.js) derives the attempted
+drag and return from that frame, sharing the object's displacement with the pointer. `fail` is this
+component's vocabulary, not a special event known to Hypit. Moving the spoken anchor changes when
+the event happens; changing the animation changes how it feels.
+
+This also explains why one Take need not equal one scene. The editor develops across several spoken
+passages, while a single passage can trigger several states. Keep the temporal cause separate from
+the scope of the objects that respond to it.
+
+## Keep playing footage distinct from its frame
+
+The same accepted presenter footage appears full-frame, in a circular inset and through a moving
+viewport. The short return to the inset on “我们继续” is a Performance Use applied to existing media.
+The camera presentation changes while the source playback continues. The
+[opening system](../../packages/opening-system/README.md) owns these Styles; Main Source owns where
+they are used. Foreground and enlarged background presentations likewise share the same media sample.
+
+Covering the presenter with MG does not require producing a new audio-only Take: the voice remains
+connected separately. The opening montage and silent ending occupy authored Timeline space outside
+spoken coverage. They do not need fake empty media. An actual acted drinking passage is different:
+it has performed material whose actions and eventual words belong to its Take.
+
## Material quality starts in direction
Voice reference, Script and Action establish the intended performance. Useful direction describes an attitude the audience can hear and see, supported by a few decisive expressions or gestures. A generated actor’s request should describe the actual performance; a metaphor about graphics flying into frame belongs in component direction. Composition review then improves framing, Caption, coverage and event timing around accepted materials.
+The voice and Script changed during this production. A more representative language sample and
+durations suited to the intended delivery addressed a different problem from graphic timing. A
+requested line or performance change needs new accepted material; moving a card or changing a crop
+can reuse the current material. Preserve that distinction so composition iteration does not become
+unnecessary regeneration. The retained [direction](authors/direction.svml) and
+[performance Recipe](recipes/performance.svs) show what was actually requested.
+
## Preserve complete visual systems when changing style
Removing redundant text does not remove the need for visual detail. When the treatment changed to pink retro graphics, folder contents, editor controls and terminal activity still had to fill their roles. A shared palette made coherent updates possible; local scene code retained the details that explained each idea.
+The change from a glossy technical look to the accepted pink treatment required more than a color
+replacement: edges, offset shadows, type, texture and motion all contributed to its character. The
+flag's complex continuous shading became a small stepped raster animation. That was a better
+expression of the chosen style, not a universal argument against 3D. Judge implementation effort
+by what it contributes to the visible work.
+
+Website passages use actual recordings where page details and scrolling matter. The editor, token
+counters and comparison transformations are authored illustrations. Separating those roles kept
+recorded evidence reusable while letting component behavior remain editable. Their precise status
+is documented in [asset provenance](ASSET-PROVENANCE.md).
+
## Write motion that can be sought directly
A pointer follows an eased path; a rejected drag shares the picture’s spring displacement; typing derives its visible tail from time. None requires playback of all preceding frames. This makes exact-frame review and range rendering normal operations. A low-resolution Canvas flag was a better match for the chosen pixel language than preserving an elaborate cloth simulation.
+The hold matters as much as the entrance. A terminal should continue visibly working while that is
+the subject of the narration; a board can settle and remain as context. An event's lifetime and the
+duration of its entrance are different decisions. Review the state before, during and after a handoff
+alongside the independent presenter and Caption, where collisions or unintended gaps become visible.
+
## Use Studio to discuss intentions
Many valuable comments describe a new visual idea, not a number a user can edit. Time-stamped comments kept that discussion attached to the picture. Companions expose only useful identifiers, timing and directing controls, through Studio’s common interfaces. A coordinated scene does not need controls for every internal measurement.
+Changing the flag's motion language or the whole treatment called for interpretation and source
+edits. Adjusting Caption position and color could use existing controls. Both are useful forms of
+review. A comment's time identifies the visible symptom; a correction to a shared style may apply
+throughout the film. Browser review made these decisions available without repeatedly exporting
+the entire video. The portable example starts without the production's private comments.
+
## Preserve accepted outputs and readable authoring
Run Candidates express which existing material to carry forward. Build execution handles the remaining work. Keep explicit output boundaries where the Run needs to select them; separate Script and direction without hiding those boundaries. Archive obsolete experiments so the active entry is evident. Keep CSS and frame programs readable rather than compressing a complete scene into a single enormous string.
@@ -31,3 +121,15 @@ Run Candidates express which existing material to carry forward. Build execution
## Export for the machine actually available
The full film temporarily exceeded local disk capacity while lossless frames accumulated. Consecutive range renders bounded temporary storage; eight workers handled each range and the output parts were joined. This is a production workaround for this machine, not a requirement for every video or a new rendering abstraction.
+
+## Carry the reasoning into another work
+
+Trace a revision to the fact it changes: the material, its placed time, a semantic event, the
+presentation, a scene's behavior or a shared design decision. That gives the next edit a useful owner.
+Copy a component when its relationship fits; adapt or author one when the new work asks for a different
+relationship. The example is useful even when none of its finished scenes should be reused verbatim.
+
+General production guidance lives in the
+[presenter-led visual explainer playbook](https://github.com/hypit-ai/hypit/blob/main/skills/hypit/references/playbooks/formats/presenter-led-explainer.md)
+and its linked crafts. These notes preserve the concrete reasoning behind this work rather than
+making its production history a required workflow.
diff --git a/skills/hypit/SKILL.md b/skills/hypit/SKILL.md
index 14feb7e9..b1b96114 100644
--- a/skills/hypit/SKILL.md
+++ b/skills/hypit/SKILL.md
@@ -86,7 +86,11 @@ For creator-led social video, favor compelling casting, an appealing voice and a
toward the subject and listener. Let that relationship shape expression and timing. Humor, contrast
or surprise needs an expression the audience can experience in the work.
-Before writing or adapting an image prompt, read [Image direction](references/playbooks/craft/image-direction.md).
+**Before writing or adapting an image prompt, read
+[Image direction](references/playbooks/craft/image-direction.md) and the chosen Kit.** This is
+empirical knowledge of how the image model responds, including capture wording and high-leverage
+casting and composition anchors; general prompting fluency does not reliably supply it. Carry the
+relevant findings into the actual prompt, using the examples to understand their force and scope.
Before choosing or changing a voice, read [Voice direction](references/playbooks/craft/voice-direction.md).
Before writing or adapting a video prompt, performance Recipe or action, read
[Video direction](references/playbooks/craft/video-direction.md) and the selected Kit's wording and choices.
@@ -224,8 +228,10 @@ practical, revisit that choice and carry the improvement into the work and its n
relevant Skill references, Sources, Runs, project Results and Runtime status.
The project-files reference below owns document responsibilities and the suggested layout.
- **Project ownership.** Preserve unrelated Source, Recipe, Run, assets, and project-package work.
- Make production changes at their owning source; keep Result media intact. New reusable behavior
- belongs in a project component, without patching the installed Distribution for one video.
+ Make production changes at their owning source; keep Result media intact. Author new visual
+ behavior in project components. When execution problems arise, actively investigate and pursue
+ a suitable repair through the [integration guidance](references/environment/model-and-provider.md),
+ explaining material changes and what they establish.
- **Done means watched.** Watch and listen to the actual deliverable and judge it against the Brief,
Treatment, and relevant reference relationships. Judge its performance, sound, clarity, visual
hierarchy, timing, character, and suitability for publishing. Browser review can settle the composition before export; when
diff --git a/skills/hypit/references/playbooks/formats/narration-led-demo.md b/skills/hypit/references/playbooks/formats/narration-led-demo.md
index 93304c05..94dec004 100644
--- a/skills/hypit/references/playbooks/formats/narration-led-demo.md
+++ b/skills/hypit/references/playbooks/formats/narration-led-demo.md
@@ -17,6 +17,8 @@ on-camera delivery. A mixed work can move between these relationships when the s
State that relationship in Treatment. It determines how performance, picture coverage, visual
proof, and later review should be understood.
+[Presenter-led visual explainers](presenter-led-explainer.md) covers the related form whose accepted
+on-camera performance remains available while demonstrations and graphics lead much of the picture.
## Direct one spoken spine and many visual answers
diff --git a/skills/hypit/references/playbooks/formats/presenter-led-explainer.md b/skills/hypit/references/playbooks/formats/presenter-led-explainer.md
new file mode 100644
index 00000000..7edefd06
--- /dev/null
+++ b/skills/hypit/references/playbooks/formats/presenter-led-explainer.md
@@ -0,0 +1,134 @@
+# Presenter-led visual explainers
+
+Read this when a spoken performance carries an explanation while demonstrations, comparisons and
+motion graphics develop much of its visual argument. The presenter may lead the frame, share it,
+move into an inset or disappear behind another contribution. Complexity comes from relationships
+developing together, not from a required number of effects or components.
+
+## Follow the argument through changing objects
+
+Understand what the audience should grasp and how the picture makes it graspable. A comparison
+can begin with two alternatives, keep them visible as the explanation examines each, then change
+their relationship when a third possibility appears. The continuing objects give the viewer a
+memory of the argument. Their entrance, movement, settled state and eventual departure all matter.
+
+Read the reference's speech and picture together through
+[transcript-linked grids](../../creation/reference-video.md). Change the range and sampling interval
+around the question being investigated: a whole passage reveals the argument, while a short handoff
+reveals whether an object was replaced, moved, cropped or covered. Let each observation revise the
+whole-piece reading, and share the understanding as it develops. A list of pictured nouns leaves
+out the behavior that makes the sequence worth recreating.
+
+For the target, express the useful relationship with its own subject and evidence. A failed action
+needs an attempted action and a perceptible consequence. A claim about reuse needs a recognizable
+structure whose content changes while its useful behavior survives. Exact wording can stay in
+Caption while objects demonstrate what the words mean. Graphic text has a separate job when a label,
+number or comparison helps the viewer read that demonstration.
+
+## Compose the performance and its presentation independently
+
+A Take supplies accepted performance, media and local word timing. Place it on the complete Timeline;
+the picture's arrangement can change several times during that same Take. A new layout usually calls
+for a presentation change, while a different spoken line or acted beat may call for new material.
+One scene may also develop across several Takes. Spoken segment boundaries do not prescribe scene
+boundaries or camera cuts.
+
+Use [Performance](../../production/performance.md) for presentation of the Timeline's existing visual
+material and [Media](../../production/media.md) for independent supplied material. A full-frame view,
+a circular crop and a moving viewport can share the same playing source. Its playback clock continues
+while the frame moves; foreground and enlarged background views of that source need the same sample.
+Let the visual emphasis follow who or what currently carries the idea, including returning to the
+presenter for an expressive reaction or direct address.
+
+Speech sound remains an independently connected contribution when MG covers the presenter. Genuinely
+independent narration uses the [narration-led relationship](narration-led-demo.md). A montage or silent
+ending can occupy ordinary time outside any Take: the complete Timeline has room for both semantic
+anchors and independently authored events. No invented performance is needed to create that room.
+
+## Give events meaning and transitions duration
+
+Name the spoken idea that motivates a change in Script, then connect its Moment or Selection to the
+component. That establishes why the event happens there. Local durations and easing establish how
+the change unfolds. A phrase can start a movement that continues into the next phrase; the settled
+state can remain useful long after the entrance finishes.
+
+Design handoffs from the states on both sides: what remains present, which geometry should meet,
+and where attention should land. A brief presentation Use can connect two longer treatments without
+changing the underlying footage. Read the actual contribution's interval and override semantics;
+shared timing does not make independent Tracks mutually exclusive.
+[Temporal projection](../../production/track-authoring.md#keep-selection-projection-and-consumption-distinct)
+and the owning component documentation supply exact syntax.
+
+## Choose a visual language, then complete its systems
+
+Turn the intended character into palette, type, edge treatment, depth, texture and motion choices.
+Judge them together in a representative passage with actual media. A style change can alter all
+these relationships: recoloring a glossy interface alone may leave its old visual character intact.
+Keep the accepted shared decisions in Recipes or ordinary code dependencies so related scenes evolve
+together. Specific colors and effects belong to this work's Treatment.
+
+Choose the realization that expresses the desired appearance well. A small raster animation can be
+right for a stepped pixel flag; a different work may need continuous cloth motion or true geometry.
+The reference supplies the appearance and behavior to understand, not a compulsory implementation.
+
+Preserve the detail that makes the scene convincing when simplifying it. Removing a redundant title
+changes the remaining layout; a folder still needs readable contents, and a working terminal needs
+visible activity while the narration describes it. A demonstration has a designed hold as well as
+an entrance. [Graphic composition](../craft/graphic-compositions.md) owns this visual judgment.
+
+## Organize the behavior at its useful scale
+
+Separate contributions that have independent reasons to change. Keep an interacting pointer, dragged
+object and destination together when they share geometry and motion. Ordinary functions and modules
+can organize their implementation; they need not each become a Track or package. A shared palette
+has code consumers without becoming a visible object.
+
+Supply the inputs the production actually directs: selected assets, meaningful events and useful
+presentation choices. A one-off scene can retain fixed internal dimensions and artwork. Caption
+position or color may deserve Inspector controls while a redesign of an illustrated editor belongs
+in its code. Independence, parameterization and cross-project reuse remain separate decisions;
+[Component design](../../production/component-design.md) owns that distinction.
+
+Make frame evaluation describe the current state, including before and after each event. Then a
+direct seek, a nearby-frame inspection and a range render can show the same designed behavior.
+Derive connected motion from shared layout so moving a target also moves its pointer destination.
+[Drawing](../../production/component-visuals.md) explains the browser-program implementation.
+
+## Develop the work with visible feedback
+
+Use generated material for the photographed or illustrated content it should actually contain.
+Use recorded interfaces when their literal state and actions are evidence; keep a recording as
+reusable material whose crop and timing can be revised. Authored MG can demonstrate a relationship
+without pretending to be a measured product recording. Material direction and reference relationships
+belong to their [Craft pages](../index.md#craft).
+
+Review a useful passage in its surrounding composition as the design develops. Explain what it
+demonstrates and what is still being built. Comments can carry a change of visual idea that no
+parameter panel can express; Studio exposes the Timeline and the choices that are useful to adjust.
+Follow a timestamped comment to the responsible Source, Recipe, media or scene implementation.
+The timestamp locates evidence; the desired change may concern a recurring system throughout the work.
+
+Preserve accepted material through explicit Run choices while revising the composition. Seek and
+review the changed action and its handoffs; export the encoded film when that deliverable is wanted.
+[Review](../../production/review.md) and [Studio](../../production/studio.md) own the interaction;
+[Rendering](../../production/rendering.md) owns render scope and resource choices.
+
+## Study one complete production
+
+The [complex spoken explainer](https://github.com/hypit-ai/hypit/tree/main/examples/complex-explainer)
+is a finished 137-second example with 17 accepted Takes. Its guide links the film, editable sources,
+media archive and project packages. Reading its code and notes needs no media download; opening the
+full picture uses the supplied media/Result archive. The default Run reuses that accepted material.
+
+| Question to trace | Concrete source |
+| --- | --- |
+| How did the design change, and what made the revisions useful? | [Treatment and craft notes](https://github.com/hypit-ai/hypit/blob/main/examples/complex-explainer/productions/explainer/CRAFT-NOTES.md) |
+| How does a spoken phrase become a scene event? | [Script](https://github.com/hypit-ai/hypit/blob/main/examples/complex-explainer/productions/explainer/authors/script.svml) and [Main Source](https://github.com/hypit-ai/hypit/blob/main/examples/complex-explainer/productions/explainer/authors/main.svml) |
+| How do existing footage, a moving viewport and independent graphics coexist? | [Opening system and Performance Styles](https://github.com/hypit-ai/hypit/blob/main/examples/complex-explainer/packages/opening-system/README.md) |
+| What belongs inside a coordinated demonstration? | [Scene map, inputs and internal modules](https://github.com/hypit-ai/hypit/blob/main/examples/complex-explainer/packages/web-scenes/README.md) |
+| How can Caption stay independently editable? | [Project Caption package](https://github.com/hypit-ai/hypit/blob/main/examples/complex-explainer/packages/single-line-captions/README.md) |
+
+Carry the reasoning into the new commission: identify which objects, relationships and events it
+needs, then author that model. This example's scene inventory, pixel treatment and export settings
+belong to its production; the other [video examples](https://github.com/hypit-ai/hypit/tree/main/examples)
+show different useful organizations.
diff --git a/skills/hypit/references/playbooks/formats/talking-head.md b/skills/hypit/references/playbooks/formats/talking-head.md
index 9607e90e..f57e440b 100644
--- a/skills/hypit/references/playbooks/formats/talking-head.md
+++ b/skills/hypit/references/playbooks/formats/talking-head.md
@@ -3,6 +3,8 @@
A compelling person speaks to the viewer. Their attitude carries the piece; Caption, evidence and MG
help the viewer follow it. A ranking board is one possible companion, not a requirement of UGC.
For that relationship, combine this page with [Ranking](ranking-listicle.md).
+When evolving demonstrations and MG carry much of the argument, use
+[Presenter-led visual explainers](presenter-led-explainer.md) for their relationship to that performance.
## One useful image can carry the whole performance
diff --git a/skills/hypit/references/playbooks/index.md b/skills/hypit/references/playbooks/index.md
index bce093c0..c13b5be4 100644
--- a/skills/hypit/references/playbooks/index.md
+++ b/skills/hypit/references/playbooks/index.md
@@ -56,6 +56,7 @@ unless the decision has changed.
| [Two-person podcast](formats/two-person-podcast.md) | complementary host views, conversational reactions, product interaction or lifestyle coverage |
| [Street interview](formats/street-interview.md) | a motivated encounter, guest/interviewer/shared views, reveals or tracked Caption |
| [Ranking and listicle](formats/ranking-listicle.md) | a persistent comparison or board whose state changes with the argument |
+| [Presenter-led visual explainer](formats/presenter-led-explainer.md) | spoken performance joining evolving demonstrations and MG, with the presenter moving between full-frame, inset and covered views |
| [Narration-led work](formats/narration-led-demo.md) | independent narration organizing products, hands, screens, demonstrations, montage, or MG |
A format page is useful when its relationships illuminate this work. It is not a category the
diff --git a/skills/hypit/references/production/component-design.md b/skills/hypit/references/production/component-design.md
index ee62b895..1d8a997f 100644
--- a/skills/hypit/references/production/component-design.md
+++ b/skills/hypit/references/production/component-design.md
@@ -105,6 +105,9 @@ coordinated explainer scenes. Trace why a behavior has its owner, what drives it
inputs a changed brief would replace. Their notes explain those choices; the scene lists are each
production's design. In the explainer, scenes retain fixed internal details while Script events,
Caption and presenter framing remain independently authored.
+For that whole-work relationship, read [Presenter-led visual explainers](../playbooks/formats/presenter-led-explainer.md).
+The [explainer's craft notes](https://github.com/hypit-ai/hypit/blob/main/examples/complex-explainer/productions/explainer/CRAFT-NOTES.md)
+trace concrete revisions back to their design decisions and source owners.
## Let meaning drive the behavior