Pairs

Use pairs when two conditions are clearly working together and one term alone would be too blunt.

Active grammar layer

Use pairs when two conditions are clearly working together and one term alone would be too blunt.

Some entries on this page are marked provisional. That means they are published here, but still under review.

A person reaches the point of entry, but the real gate is hidden.

Use this pair when access looks open on paper, but the actual crossing depends on permission, proof, reassurance, or another hidden condition.

Short example. A booking link is live, but a person only learns at the final step that a staff member has to approve the request first.

The service has a path, but breaks in the path are hard to recover from.

Use this pair when the sequence exists, yet a pause, failed handoff, or missed step leaves the person unsure how to continue.

Short example. A repair visit is missed, and the tenant has to start several steps again because the case no longer has a clear route.

The experience depends on hidden coordination and a handover that is not holding.

Use this pair when the service only works if information or responsibility moves cleanly between teams, systems, or roles.

Short example. Support, scheduling, and the contractor all touch the case, but each receives a slightly different version of it.

People need safe pause and re-entry, not just a way to continue.

Use this provisional pair when the service has to support recovery and return together, especially after a setback or failed attempt.

Short example. A patient misses an appointment and needs both reassurance and a clear route back into care.

The path only works if it contains places to pause and regroup.

Use this provisional pair when forward movement depends on built-in pause, reassurance, or protected reset within the route itself.

Short example. A long support process needs clear holding points so people can stop, regroup, and continue without losing their place.