Glossary of Terms

This page defines key terms used throughout NOX. These definitions are short, structured, and link back to where they appear in use. The goal is to reduce ambiguity and make the system's vocabulary accessible to others.

Term	Definition	Appears In
`emit_to`	Directive that routes content from one log to a new file when a threshold is hit.	Protocol, Thresholds
`referencable emittance`	A captured fragment (idea, task, log) that can be retrieved and reused over time.	Logs
`SYS Interrupt`	Signal that current work needs to break off into a new track or log context.	Thresholds
`signal`	A log mode that captures emotional, strategic, or cognitive state.	Protocol
`model`	A named object or topic being tracked over time (e.g., wallplates, port logs).	Create NOX
`threshold-based development`	Strategy for creating structure only when natural limits (size, reuse) are hit.	Thresholds
`handoff`	A packaged file or log meant to be read by someone else — usually triggers README.md creation.	Thresholds
`imploded string`	A collapsed structure where multiple concepts are buried in a single dense file or paragraph.	Logs
`archive.log`	Historical changelog that records major edits or file transitions over time.	Logs
`daily file`	The container folder (e.g., 07-13-homework) for the day's work, logs, signals, and models.	Create NOX

← Back to What is NOX
← Return to Portfolio Home