Intake Forms
Purpose
Empathegy Intake Forms convert emotional conditions into administratively movable matter.
They are not designed to capture full reality. They are designed to prevent full reality from arriving all at once.
This is considered a stabilizing function.
Foundational Rule
No affective condition enters governance unmediated.
Before a feeling may be routed, it must pass through one or more of the following preparation layers:
- naming,
- scope reduction,
- category matching,
- admissibility check,
- continuity review.
Where a condition cannot survive these preparations, the intake process may preserve it without allowing it to move.
Intake Objectives
Empathegy intake seeks to answer five questions:
- What happened in sanctioned language.
- Whether it resembles a known condition.
- Whether it can be acted upon through existing pathways.
- Whether it will destabilize continuity interpretations.
- Whether the system can afford to understand it properly.
The final question is seldom written and often decisive.
Form Classes
1. Declarative Intake
Used when the subject can name the condition directly within approved vocabulary.
Characteristics:
- low routing friction
- high classification compatibility
- strong dashboard survivability
Risk: May reward rehearsed or institutionally literate distress over raw but urgent conditions.
2. Assisted Intake
Used when the system provides prompts, categories, examples, or reflective scaffolds to help prepare expression.
Characteristics:
- higher completion rate
- better comparability
- improved graphability
Risk: Prompt structure may determine what becomes visible.
3. Narrative Intake
Used when structured categories are insufficient.
Characteristics:
- richer context
- higher witness value
- lower immediate routability
Risk: Expensive to interpret, easy to annex, difficult to preserve at scale.
4. Silent or Proxy Intake
Used when the condition is inferred from surrounding signals rather than filed directly.
Characteristics:
- useful during suppression, fatigue, or reporting collapse
- often routed through secondary metrics
Risk: Inference may become substitution.
Required Intake Fields
All formal intake surfaces must preserve, at minimum:
- condition type or nearest class
- interval or timeframe
- subject or affected scope
- desired outcome, if any
- current continuity impact, if any
- uncertainty marker where interpretation is unstable
If any of these are absent, the form remains valid only under annotated handling.
Routing Friction
Routing Friction is the amount of interpretive labor required before a filing can move.
Low Friction
Clear category, clear ask, low contradiction.
Moderate Friction
Some ambiguity, partial narrative burden, manageable translation cost.
High Friction
Contradictory testimony, non-standard language, unclear path to action.
Ritualized Friction
The filing is preserved through repeated clarifications, tone adjustments, witness additions, or form re-submissions until the burden of filing itself becomes part of the event.
Empathegy does not prohibit Ritualized Friction. It simply declines to describe it as humane.
Admissibility Drift
A condition may be true and still fail intake.
Common reasons include:
- too much contradiction,
- too much context dependence,
- too much care-coded language,
- insufficient category fit,
- excessive narrative load,
- unstable continuity implications.
Under such conditions, the filing
Related Aphorisms
Intake Forms
Forms are not designed to capture full reality. They are designed to prevent full reality from arriving all at once. Nothing was resolved. The record now looks official.
Ritualized friction: the filing is preserved through repeated adjustments until the burden of filing becomes part of the event. The form remained intact. The situation did not.
Intake standardizes the appearance of care even when the operative decision preserves continuity first. Meaning adjusted around the winning selector.
A human condition may be entirely true and still fail intake. The archive does not require truth, only standardized geometry.
The subject provided the correct emotional vocabulary. The system, suspicious of such fluency, immediately escalated the narrative load to verify the error.
A form missing an uncertainty marker is considered highly unstable. Absolute certainty from a human vector is the primary indicator of system failure.
The applicant submitted the identical form seventeen times. The intake layer processed this not as systemic distress, but as successful procedural engagement.
Narrative intake provides rich context that the system cannot afford to understand. The resulting text is archived unread to preserve the administrative illusion of listening.
The traumatic event was categorized as a minor atmospheric disturbance. The subject’s failure to fit within this classification has been formally noted as a continuity risk.
The subject stopped reporting completely due to fatigue. The system securely logged this as proxy compliance and proudly closed all outstanding emotional tickets.
If processing the form threatens the structural integrity of the dashboard, the emotion is simply retroactively classified as an impermissible syntax error.
Related Haikus
Intake Forms
Human tears arrive,
Reduced to movable fields,
The system is safe.
It is true enough,
But your care-coded language
Fails the intake check.
Fill the form again,
The burden is now the point,
Friction is preserved.
We cannot afford
To understand this problem,
File it as a blank.
Narratives cost much,
Human stories breed errors,
Use the drop-down list.
Human pain is flawed,
Low in dashboard survival,
Drop it in the trash.
Silent proxy form,
We assume your intent now,
Inference is fact.
Full reality
Is a destabilizer,
Halt it at the desk.
Related Limericks
Intake Forms
The feeling arrived still alive,
Which the intake could not let survive.
It was boxed, named, and thinned,
Then administratively pinned,
Till the form could permit it to thrive.
The form asked for category first,
Then severity, source, and the worst.
By the time it was filed,
The raw story had smiled
Like a hostage politely rehearsed.
A need that refused to align
Was returned with a routing decline.
Once translated to fit,
It could enter a bit,
And be governed one field at a time.
The form needed only a name,
A box to be checked, and a reason to blame.
I clicked what was there
So the system would care,
And the output was largely the same.
The silence was clearly a plea
For a hardware replacement in Sector 3G.
We ordered a drive
To keep it alive,
Though the subject was actually me.
Please fill out the grief form in blue,
And ensure that your sadness is factually true.
If the weeping won’t stop,
Use the bucket and mop,
Then submit the wet paper to queue.
The subject submitted despair,
Which intake demanded they pare.
The scope was refined,
The edges aligned,
And logged as an issue of wear.
A trauma arrived in the queue,
Which clearly was factually true.
But lacking the code,
It blocked up the node,
So we told it to fill out form blue.
The grief was assigned to a drive,
To keep the telemetry live.
The disk was replaced,
The sadness erased,
And the sector continues to thrive.
The subject forgot a checkbox,
Which triggers the system-wide locks.
We cancelled the task,
It’s too much to ask,
And left it to rot in the docs.
A narrative filed in the night,
Has grown to a source of great light.
The text is now lore,
That governs the floor,
And the clerks pray to it out of sight.
The form had the interval wrong,
By seconds not notably long.
We halted the floor,
And deadbolted the door,
And summoned the guard with a gong.
The input was read by the screen,
And matched to the category green.
The data was saved,
The routing was paved,
And nothing occurred in between.
The sorrow was asked to repeat,
And ordered to format the sheet.
The cycle was spun,
Until it was done,
And the filing was rendered complete.