Gordian Lock: Operating and Control

The distinction is functional

The archive-supplied description says both keys could lock and unlock the Gordian lock. The check key could also modify which other key remained useful.

The distinction is between exercising an existing permission and changing an authorisation relationship. Two holders can share one capability without sharing all of them. This is a conceptual reading of a historical object description, not instructions for altering or bypassing a lock.

Sources for this section: [1]

Keep the neighbouring object stories distinct

The same exhibition separately labels a springless-lock patent.

The company biography discusses Ardeshir and Pirojsha together.

The later newspaper account distinguishes the 1908 application from the 1909 grant and says the certificate credits Pirojsha.

The original certificate was not inspected here. The supported conclusion is that a founder biography, a patent story and a functional description should not be fused into a single sole-inventor claim. Nor does a security product’s historical promotion independently prove an absolute performance guarantee.

Sources for this section: [1] · [2] · [3]

Original task: complete a permission matrix

In this stipulated classroom model, ordinary means operate; check means operate and change access. Use columns “operate” and “change access”, and rows O and C. Fill each cell with yes or no. The labels are abstractions of the stated distinction, not a modern product specification.

Test three proposed sentences: A, “O may operate”; B, “only C may operate”; and C, “O may change access because O may operate”. Identify which follows from the supplied model. Do not add a physical procedure, a guessed key shape or a claim about every lock with two keys.

Sources for this section: [1]

Reference answer: shared use, unequal control

The matrix is O: yes/no; C: yes/yes. A follows. B is false because the first capability is shared. C does not follow because the second capability has not been assigned to O. These are deductions from the stipulated permissions.

The stronger reading preserves the two columns rather than collapsing them into a single powerful/not-powerful label. A role can have the right to use a system without the right to change who else can use it. The historical description supplies the distinction; the table is an original way to make its logic explicit.

Sources for this section: [1]