Spike Marking System Glow Tape Color Code Chart
Bounded offline reference: Spike marks record verified scenic/performer positions using a production-specific code. Source: Stage-management practice. No universal tape-colour code or inference that a marked position is safe/authorized. Only explicit topic keys supported: summary, reference, limitations. No complete external corpus, live data or personal assessment implied.
Description
Spike marks identify documented scenic or performer positions using a production's adopted code.
Spike marks identify documented scenic or performer positions using a production's adopted code.1
Tape colors do not form one universal naming scheme.
When to use Spike Marking System Glow Tape Color Code Chart
Use this tool to read a bounded explanation for an exact reference topic. Establish the production, adopted practice, equipment configuration and applicable source or policy edition.
How to use Spike Marking System Glow Tape Color Code Chart and understand its results
- Establish the production, adopted practice, equipment configuration and applicable source or policy edition.
- Enter topic, using the field meanings and rules below, then run the tool.
- Read result.text for the exact selection. Use its qualifications when relating the explanation to your actual production or assessment.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| topic | Topic | string | Required |
Choose one exact topic token from the table. The implementation looks up the stored value and returns it in the documented output field. Matching is case-sensitive; unrecognized tokens fail. This is an offline bounded reference, not a live catalogue or independent attribution.
| Topic token | Stored value |
|---|---|
| summary | Spike marks record verified scenic/performer positions using a production-specific code. |
| reference | Stage-management practice. |
| limitations | No universal tape-colour code or inference that a marked position is safe/authorized. |
value=referenceTable[exactToken] Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or qualified reference | object |
| result.text | Stored explanation for the exact selected topic or grade token. | string |
{
"input": {
"topic": "summary"
},
"output": {
"result": {
"text": "Spike marks record verified scenic/performer positions using a production-specific code."
}
}
}Limitations and assumptions
The actual production context, equipment configuration and applicable reference must be independently established. A recorded reference or calculation does not authorize a procedure or demonstrate compliance. No universal tape-colour code or inference that a marked position is safe/authorized.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Tech Table Sightline House Half Position Lookup: A technical table's position affects the production team's viewing and access conditions. For a complementary comparison, use Headset Etiquette Caller Standby Expect Go Discipline: Standby and go serve different functions in an adopted cue-calling protocol.
References
Similar or alternative tools
- Tech Table Sightline House Half Position Lookup
A technical table's position affects the production team's viewing and access conditions.
- Headset Etiquette Caller Standby Expect Go Discipline
Standby and go serve different functions in an adopted cue-calling protocol.