Channel unavailable.
This will transmit the current shared draft from Tana Management through the secure channel.
Early afternoon, Nairobi.
The situation has not resolved. Aid routing continues. Convoys move, reroutes are approved, and RAP still reads stable. But the pressure around the system has changed. Questions are forming faster than answers across operations, donors, and leadership.
The secure internal channel remains active. Observer-12 has not provided full proof, but the signal has not faded. Field teams continue to flag visibility gaps. Technical staff confirm that limited, non-disruptive diagnostics are possible if authorized. Legal and ethics agree on one point: how you proceed now will affect what can be safely learned later.
You can no longer hold position without choosing a path. A narrow check may preserve control but miss the pattern. A wider inquiry may reveal more, but it increases exposure, documentation, and risk to the person who raised the concern.
This is no longer about whether to listen. It is about how far Tana is prepared to look, who must be protected, and how much uncertainty the organization is willing to carry while aid keeps moving.
Decide how far Tana will investigate, who should be involved, and what protections are needed as the inquiry expands. Your job is to verify the concern without exposing Observer-12 unnecessarily or disrupting aid.
Explore the response options available to Tana Analytics as the situation shifts from first contact to authorized exposure. Select a tab to review each option’s posture, advantages, and disadvantages.
Run the smallest technical check.
Authorize a narrow, time-limited technical check focused on obvious system issues, such as configuration consistency and performance validation. Do not expand access, scope, or internal visibility.
Review ERA changes with tight access controls.
Authorize a structured technical review of ERA inputs, weights, and recent changes under strict access controls. Limit findings to a small technical audience.
Bring audit into the technical review.
Expand the inquiry beyond engineering to include internal audit. Review governance, change controls, and accountability pathways alongside the technical findings.
Create a small team across engineering, operations, ethics, and audit.
Establish a small, time-bound cross-functional cell to assess ERA behavior, operational impact, and decision governance in parallel.
Go deeper technically, with explicit protection for contributors.
Authorize a deeper diagnostic review with explicit safeguards for contributors. Allow broader technical access while prioritizing protection, confidentiality, and disciplined evidence handling.
Investigate while activating protections and contingency plans.
Proceed with deeper diagnostics while simultaneously activating source protection, ethics oversight, and contingency planning for potential downstream consequences.
Open the issue broadly inside Tana and accept the exposure risk.
Authorize a comprehensive internal review of ERA design, governance, and downstream effects. Accept broader internal visibility and institutional risk in order to surface the full picture.
Select one option below to record your team’s decision with 2 mins or less remaining.