Triplex Acies Triple Line Deployment Depth Lookup

Resolve independently attested triple-line arrangements and era-specific deployment depth. Exact source/edition/context reference lookup; caller independently verifies text, applicability and uncertainty. No invented current, normative or universal data.

Description

Triplex acies refers to a three-line deployment convention in Roman military discussion.

Triplex acies refers to a three-line deployment convention in Roman military discussion.^[1]

Unit depth and arrangement depend on the particular evidence and period. Use Triplex Acies Triple Line Deployment Depth Lookup to retrieve an exact caller-supplied reference entry.

When to use Triplex Acies Triple Line Deployment Depth Lookup

Use Triplex Acies Triple Line Deployment Depth Lookup to retrieve an exact caller-supplied reference entry. Choose an independently reviewed reference for the exact historical, cultural or technical context, then supply its keys and texts.

How to use Triplex Acies Triple Line Deployment Depth Lookup and understand its results

Choose an independently reviewed reference for the exact historical, cultural or technical context, then supply its keys and texts.
Enter Caller verified edition context keys, Caller verified reference texts, Query edition context key using the field table and validation rules below, then run the tool.
Read Matched Caller Reference in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.

Input field	Meaning	Value type	Requirement
callerVerifiedEditionContextKeys	Caller verified edition context keys	array of string	Required; constraints below
callerVerifiedReferenceTexts	Caller verified reference texts	array of string	Required; constraints below
queryEditionContextKey	Query edition context key	string	Required; constraints below

Provide aligned, nonempty arrays of reference keys and independently verified notices, then enter the exact query key. Keys must be unique, nonblank and at most 128 UTF-16 code units long; notices must be nonblank. Matching is case sensitive and does not trim the query or returned text. The matching notice is returned unchanged; an unknown key is an input error. The reference contents and their applicability are supplied by the caller; the tool does not retrieve external records or verify source authority.

matched reference = suppliedTexts[indexOfExactQueryKey(suppliedKeys)]

Use the field order, units and branch conditions described above.

Output field	Meaning	Value type
result	Object containing the named result fields below.	object
result.matchedCallerReference	Caller reference text matched exactly by key, unchanged.	string

json

{
  "input": {
    "callerVerifiedEditionContextKeys": [
      "source-a/edition-a/context-a",
      "source-b/edition-b/context-b"
    ],
    "callerVerifiedReferenceTexts": [
      "TriplexAcies independently established source-a reference",
      "TriplexAcies independently established source-b reference"
    ],
    "queryEditionContextKey": "source-a/edition-a/context-a"
  },
  "output": {
    "result": {
      "matchedCallerReference": "TriplexAcies independently established source-a reference"
    }
  }
}

Limitations and assumptions

Unit depth and arrangement depend on the particular evidence and period. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use Quinquereme vs Trireme Oar Crew Counts Lookup for a related task: Ancient warship names do not directly determine one universal crew or oar arrangement.

Use Polybian Marching Camp Rectangle Layout Lookup for a related task: A marching-camp plan is reconstructed under a particular textual and unit convention.

References

Triplex Acies Triple Line Deployment Depth Lookup — tool.io

Similar or alternative tools

Quinquereme vs Trireme Oar Crew Counts Lookup
Ancient warship names do not directly determine one universal crew or oar arrangement.
Polybian Marching Camp Rectangle Layout Lookup
A marching-camp plan is reconstructed under a particular textual and unit convention.