Form column in order of sequence numbers; steer course 116; proceed at 16 knots.
Expected code:FORM 1 - CORPEN A - 116 - SPEED H - 16
Transmission context optional
What this changes: context tells the translator how a signal is being sent. For encoding, your ship is the sender. The Visual hoists module is separate and does not affect translation unless you explicitly select translation evidence for a Chapter 2 meaning that depends on physical position, state, or layout.
Enter an instruction and translate it.
Open Visual hoists and choose From Encode to build or replay the flag display.
Use translation evidence only when a physical display is part of the meaning.
Stored flag operating context
Operating uses, ship roles and selected materials are remembered for later radio announcements, including after reopening this browser. Choose every known material, or leave it unspecified. The flag does not transmit separate material operands. Each new report updates the last display state; you can edit or remove the stored context.
Own ship · sender
Other ship · addressee
Visual hoists and layout
Model each ship separately. A display zone is an MTP location such as mainmast starboard outboard; it may contain several independent halyards. Generic slot counts are visual capacity hints, not an MTP rule. Choose a vessel-specific profile when the real ship's named halyards are known. Mark the planned hoist as focused when encoding.
Build a flaghoist from the translated codeThe sender is your ship. Each build uses the current English input, translating it first if needed. Existing flying hoists are carried into the new exchange when accumulation is enabled.
Own ship hoists
Hoist list and rig settings
A slot represents one independently usable halyard. Capacity is vessel-specific.
Other ship hoists
Hoist list and rig settings
A slot represents one independently usable halyard. Capacity is vessel-specific.
Cmd/Alt + Enter
Output
Samples
Decode
Code → English
InputTransmission context optional
What this changes: context records what you can observe outside the code string. For decoding, the other ship is the sender. The Visual hoists module is separate and does not alter an ordinary decode. Select translation evidence only when Chapter 2 says that physical position, state, duration, or a relationship between hoists is part of the meaning.
Enter the received code and translate it.
Open Visual hoists and choose From Decode to build or replay the flag display.
Use translation evidence only when a physical display is part of the meaning.
Stored flag operating context
Operating uses, ship roles and selected materials are remembered for later radio announcements, including after reopening this browser. Choose every known material, or leave it unspecified. The flag does not transmit separate material operands. Each new report updates the last display state; you can edit or remove the stored context.
Other ship · sender
Own ship · addressee
Visual hoists and layout
Model each ship separately. A display zone is an MTP location such as mainmast starboard outboard; it may contain several independent halyards. Generic slot counts are visual capacity hints, not an MTP rule. Choose a vessel-specific profile when the observed ship's named halyards are known. Mark the observed hoist as focused when decoding.
Build a flaghoist from the received codeThe sender is the other ship. Each build uses the current code, decoding it first if needed. Existing flying hoists are carried into the new exchange when accumulation is enabled.
Other ship hoists
Hoist list and rig settings
A slot represents one independently usable halyard. Capacity is vessel-specific.
Own ship hoists
Hoist list and rig settings
A slot represents one independently usable halyard. Capacity is vessel-specific.
Cmd/Alt + Enter
Output
Visual hoists and layout
Translated radio flag announcements automatically update the reporting ship’s flags. For other signals, choose a translation source and build an animation from its current code. The ships use the callsigns and roles in that source’s Transmission context. Accumulation carries forward flags still flying, not completed message animations.
Existing hoists stay flying from the first animation frame. Still views hide carried-over hoists by default. Clearing removes every displayed hoist and animation, including standing pennants, while keeping ship identity, operating conditions and rig settings. Nearby free halyards are chosen within the configured rig; generic capacity is illustrative.
Registry
SIGNAL literal<value> required[<value>] optional<value> conditional
Verified sample listGenerate the currently selected demo sample set. Single-command samples are checked against all engines; message sequences are checked only with Hybrid v3. The build runs in the background and survives re-logins.
Review
Status profiles
Create a reusable evaluation snapshot from your reviews, or exchange a JSON/JSONL profile. Choose the active profile in the Registry's Evaluation source filter.
No cases to review. Either the queue is empty or every remaining
case has been marked Correct/Skip.
Test complete conversations with explicit, reviewed operator answers. Upload the CSV in Test Suite, choose first response or supplied answers, and download scored results plus raw traces.
Download the complete typed registry, including chapters, commands, tables, grammar, and operation orders. The current global rendering settings are recorded in the export.
Review/test package
Generate validated code/English cases for offline testing or human review.
The package follows the Chapter filter currently selected in Registry. Annotated Excel packages can be imported from the Review module.
Registry import
Interactive registry replacement is intentionally unavailable until an import can be validated and previewed safely. File-based registry loading remains a server-startup operation.