DIRECTIONAL RELATIONSHIP GRAPH
The graph stores trust, protection, fear, suspicion, knowledge, and manipulation as directional edges. Labels change with the active source set; the underlying person records do not.
Guarded therapeutic trust
Mara discloses more to Sayer than to other staff but repeatedly tests her language.High clinical investment
Sayer obstructed transfer orders and duplicated the chart.Security oversight
Rook independently logs Sayer's access and communications.Requests procedural exceptions
Sayer gives Rook verifiable fragments while withholding source identity.Monitors a high-risk patient
Entry footage shows a recognition response before chart access.Avoids security contact
Mara reacts to Rook's voice, not his face.Recognizes another careful witness
Mara and Imani exchange discrepancies rather than conclusions.Tests whether Mara's claims contaminate the model
Imani validates Mara's facts while isolating claims that depend on memory.Monitors an overextended employee
Sayer repeatedly converts disciplinary events into occupational-health review.Relies on a fair supervisor
Tobias preserves copies of Sayer's written instructions.Understands the board liaison's document style
Priya recognizes originator tokens and revision habits across directives.Frames retention as a promotion opportunity
Vivian offers authority precisely when Priya's archive becomes dangerous.Questions security's undocumented network access
Naoko detects security-originated queries outside the incident scope.Monitors a contractor exceeding scope
Caleb requests raw telemetry but omits her tasking identity from reports.Accepts support from a claimed relative
Elias lowers his voice and separates facts from inference in her presence.Provides family support and de-escalation
Samira limits his public exposure and duplicates his strongest documents.Recognizes her interest in the east corridor
Anton changes maintenance timing after Mara begins testing the wall.Believes maintenance knows more than it reports
Mara marks hardware and checks whether Anton restores it.Maintains appropriate clinical restraint thresholds
Oren documents consent and medical indication before security can redefine them.Treats the medic as a continuity resource
Vivian routes operational demands through patient-safety language.Questions the timing of executive directives
Oren compares his pre-issued credential against the official incident chronology.Relies on records provenance
Imani revises conclusions when Priya supplies version history.Preserves disputed analytic attachments
Priya duplicates the source files and their transformation history.Recognizes a contractor from nonprofit infrastructure work
Samira and Naoko share a timing phrase in otherwise ordinary exchanges.Accepts a limited technical liaison
Naoko preserves one relay after Samira provides a consent boundary.Avoids direct conflict with executive oversight
Anton complies visibly while modifying systems outside the approved drawings.Accepts sleep-first care and precise uncertainty
Marcus responds when Sayer separates observed signal from catastrophic interpretation.Prioritizes stabilization over interrogation
Sayer documented that fatigue treatment and evidentiary interview must not be collapsed into one process.Treats him as a competent witness with a contaminated timeline
Imani independently reproduces the timing anomaly but not Marcus's causal explanation.Reviews infrastructure telemetry after the clinical incident
Naoko can validate the waveform but not the patient's account of a pending arc event.Keeps Mara available as a witness while resisting handler pressure
Relationship strength is directional and source-specific; it does not imply reciprocity.Conditional trust in a facilitator who names uncertainty
Relationship strength is directional and source-specific; it does not imply reciprocity.Peer disagreement over information control
Relationship strength is directional and source-specific; it does not imply reciprocity.Audits procurement conflicts
Relationship strength is directional and source-specific; it does not imply reciprocity.Provides curated finance records
Relationship strength is directional and source-specific; it does not imply reciprocity.Compares identity and payment records
Relationship strength is directional and source-specific; it does not imply reciprocity.Technical respect between linguist and collector
Relationship strength is directional and source-specific; it does not imply reciprocity.Limits his exposure to damaged audio
Relationship strength is directional and source-specific; it does not imply reciprocity.Recognizes shared language around missing time
Relationship strength is directional and source-specific; it does not imply reciprocity.Adjusts transport routes around pharmacy deliveries
Relationship strength is directional and source-specific; it does not imply reciprocity.Relies on transport timing
Relationship strength is directional and source-specific; it does not imply reciprocity.Tracks unexplained security appearances
Relationship strength is directional and source-specific; it does not imply reciprocity.Demands a named extraction promise
Relationship strength is directional and source-specific; it does not imply reciprocity.Maintains medical readiness
Relationship strength is directional and source-specific; it does not imply reciprocity.Believes Locke authorized his disavowal
Relationship strength is directional and source-specific; it does not imply reciprocity.Reviews security access anomalies
Relationship strength is directional and source-specific; it does not imply reciprocity.Challenges outside authority
Relationship strength is directional and source-specific; it does not imply reciprocity.Uses consent-bounded interviews
Relationship strength is directional and source-specific; it does not imply reciprocity.Reviews extraction medical decisions
Relationship strength is directional and source-specific; it does not imply reciprocity.Requests sponsor decision logs
Relationship strength is directional and source-specific; it does not imply reciprocity.Limits board scope
Relationship strength is directional and source-specific; it does not imply reciprocity.Restores damaged records
Relationship strength is directional and source-specific; it does not imply reciprocity.Shares archival anomalies
Relationship strength is directional and source-specific; it does not imply reciprocity.Offers identity restoration choices
Relationship strength is directional and source-specific; it does not imply reciprocity.Avoids identity interviews
Relationship strength is directional and source-specific; it does not imply reciprocity.Coordinates financial and access timelines
Relationship strength is directional and source-specific; it does not imply reciprocity.Differential reviewer preserving claim-level evidence
Laila separates Rowan’s observed lens from the wider transfer theory.Conditional trust in the review process
Rowan discloses uncertainty only after Laila acknowledges the recovered lens.Challenges global surveillance conclusions
She verifies invoices independently while declining to confirm Pavel’s wider network.Protects occupational identity during stabilization
Laila orders the transmission preserved and blocks humiliating debrief tactics.Clinical consultation on difficult cases
Their notes agree on dignity but diverge on institutional complicity.Questions sealed employment intervals
Laila flags language in old charts that resembles handler assessment.Limits access to security evidence
Rook delays logs while claiming chain-of-custody concerns.Shares procurement anomalies
Sofia confirms the vendor chain but refuses Pavel’s global attribution.Reconstructs a damaged signal
Omar validates the burst while challenging its grandiose interpretation.Accepts practical support from a recovery medic
Oren’s direct language lowers Victor’s sense of tribunal but raises old recognition.Believes the route specialist knows the tail
Marek can verify route anomalies but will not disclose his client.Offers route review and safer transport
He maps the confirmed vehicle while preserving her control over departure.Technical review of an unauthorized carrier
Their independent captures share timing drift and a retired wake signature.Separates signal fact from personalized message
Naoko reproduces the carrier but finds no addressed payload.Calls the records manager by an obsolete codename
Amina’s recognition is intermittent, but the checksum links to Priya’s sealed archive.Protects papers and supported decision-making
Priya logs every access and refuses an unsigned transfer order.Cross-checks open-source harassment evidence
They maintain separate source logs to prevent one theory absorbing the other.Respects Noor’s corrections and uncertainty
Quill publishes only claims that survive independent corroboration.Mutual protection after the break-in
Their bond preserved safety while reducing independent checking.Protects his sister from institutional pressure
Elias becomes more flexible when he knows Mira retains choice.Separates paired accounts with consent
Separate interviews reveal matching physical observations and divergent attribution.Uses tool-based reconstruction
Elias demonstrates the latch damage using a controlled replica.Frames differential review as quality assurance
Locke requests composite reliability scores that Laila refuses to produce.Rejects global witness scoring
Laila preserves the request and its metadata rather than complying.Associates security access with the transfer theory
Rowan’s fear predates confirmation that Rook inspected the sensor scene.Treats Rowan as a records-security witness
Rook verifies document access without accepting Rowan’s full explanation.Links Locke to procurement fraud
The ledger supports a payment link but not every allegation Pavel makes.Links contractor harassment to Locke’s portfolio
Noor’s source graph survives independent review.