Tack Grammar

INPUT_FORMS

The tack parser recognizes four prefix patterns, checked in priority order. Everything else is filed as hay.

→ and -> are equivalent — the parser accepts both. Priority is always: exact match first, then pattern match, then LLM inference as last resort.

TACK_EXAMPLES

$ :status
→ kernel dispatch → ostk status
   3 open needles, 2 agents alive, gen 20556

$ :compile
→ triage hay → 4 new needles filed

$ :close →573
→ needle 573 closed

$ .? how does bail work
→ LLM query → bail packs a signed artifact
   with SHA-256 manifest and attestation chain

$ →1245
→ needle 1245: "verb namespace refactor"
   status: open, priority: p1, milestone: v0.9

$ :: agent1 fix the build
→ nudge agent1: "fix the build"

$ need to refactor the auth module
→ filed as hay (raw intent)
   compile later with :compile

RESOLUTION_PIPELINE

When you type :verb, the kernel resolves it through three sources in priority order. First match wins.

If no source matches, the kernel returns up to 3 edit-distance suggestions (Levenshtein, threshold 3). The OS never says "unknown verb." It always tries.

NAMESPACE_LAYERS

Beyond the resolution pipeline, verbs are dispatched through four namespace layers. Resolution walks layers in priority order — highest-priority handler wins.

VERB_TIERS

Every verb in the .language file has a tier that determines its stability and persistence.

INTERNALIZED_VERBS

These 29 verbs resolve as direct function calls inside the kernel — zero-cost dispatch, no shell, no socket. The rest dispatch through .language, HUMANFILE, or shell.

Verbs like correct and nudge resolve to the same handler. add and needle are equivalent. search, find, and grep all route to the same search handler.

THE .LANGUAGE FILE

The verb registry. A pipe-delimited table loaded at boot. Generated by :compile from usage patterns in the audit trail.

# verb | tier | layer | last_gen | momentum | resolution | signature | doc
:boot     | 1 | kernel | 20556 | 1.00 | internal | () → (state)   | read state, report identity
:compile  | 1 | kernel | 20556 | 1.00 | internal | () → (report)  | triage hay into needles
:hay      | 3 | user   | 20556 | 1.00 | internal | (text) → ()    | capture raw intent
:shelve   | 1 | user   | 20556 | 1.00 | internal | (id) → ()      | pause needle work
:ultrathink| 3 | user  | 20554 | 0.20 | [LLM inference] | (topic) → ()   | deep reasoning

MOMENTUM

Verbs you use often get faster. Usage frequency is tracked in the audit trail. When you run :compile, the kernel rebuilds the .language file from usage patterns and updates momentum scores.

This is not LLM-learned. It is frequency-based. The verb table evolves across sessions through audit trail analysis. Over time, your tack vocabulary converges on the commands you actually use.

ALIASES

The static verb table includes aliases that resolve to canonical verbs. You can type whichever form feels natural.

HUMANFILE_VERBS

The HUMANFILE's tack grammar section defines the operator's personal dialect. Custom verbs via VERB or TACK directives.

# In .ostk/HUMANFILE:
VERB pitchfork show --semantic
VERB discuss spawn round-table
TACK boost priority-modifier

# Then in the tack bar:
$ :pitchfork
→ resolves to: ostk show --semantic

$ :discuss
→ resolves to: ostk spawn round-table

HUMANFILE verbs sit in the user:: namespace layer — lowest priority. If a kernel verb or driver verb has the same name, the kernel verb wins.