Ahmed Bakhat Masood and the PKIX Coordination Record Behind Pakistan Internet Exchange Growth

Summary

• Ahmed Bakhat Masood’s dated public record connects a Pakistan Telecommunication Authority affiliation, the role of Secretary to the PKIX Board, SANOG35 presentations and APNIC-attributed coordination across exchange points in Islamabad, Karachi and Lahore.
• The evidence supports an analysis of convening, governance and operational learning, but it does not establish personal ownership of PKIX, sole responsibility for any exchange, independently audited traffic or latency outcomes, current peer scale, private authority or endorsement by the institutions named.

A public role built around coordination

Internet exchanges are often described through equipment, traffic charts and the economic case for keeping local traffic local. Those subjects matter, but they can conceal the organisational questions that arise before networks agree to interconnect. A switch does not decide who may participate. A facility does not settle governance, cost or responsibility. The public record identifies several institutions in the PKIX process rather than a single decision-maker. This profile asks where Ahmed appears in that record without assigning duties the sources do not describe.

Ahmed Bakhat Masood appears in the public record at that coordination layer. The PKIX public board page lists Ahmed Bakhat Masood as Secretary to the IXP Board, with the Pakistan Telecommunication Authority, or PTA, as the department and regulator or government as the stakeholder representation. A 2022 APNIC Blog account identifies him as a deputy director of cybersecurity at PTA and says he assisted with coordination on the exchange points in Islamabad, Karachi and Lahore. A 2020 APNIC Blog article connects him to discussions around PKIX and to a public presentation at SANOG35. The SANOG35 programme independently records that presentation and another session under a spelling variant of his name.

Taken together, those sources support a bounded profile. They show a public responsibility chain from Ahmed to PTA, from PTA to a multi-stakeholder exchange effort, and from that effort to a formal board role and community-facing technical presentations. They do not show that Ahmed owns PKIX, controls every operating decision, founded the exchange alone or can speak for every entity. They also do not provide a complete employment history, a private biography or an audited account of individual performance.

That boundary is important because coordination roles are easily inflated. An article can turn a board secretary into an executive owner, or turn a quoted technical official into the sole architect of a national system. Neither move would be supported here. Ahmed’s documented role is narrower: APNIC reports that he assisted coordination across three exchange points, PKIX names him as Secretary to the IXP Board, and SANOG records his public presentation work.

The work described in the public accounts is consequential precisely because it is distributed. Operators retain their own networks. Facilities retain their own responsibilities. The regulator has a public role but is not a substitute for the engineering decisions of entities. Technical-community organisations can supply training, equipment or convening support without owning the resulting exchange. Ahmed is documented inside that distributed record, not above it.

The board secretary role as an accountability signal

The title “Secretary to IXP Board” sounds administrative, yet it reveals something material about the PKIX structure. A board can give entities a place to represent different interests and record decisions. The available PKIX page does not disclose Ahmed’s duties, delegated powers, work product or tenure, so it would be wrong to infer any of them from the title. It establishes only that he held a named position inside the published governance arrangement.

That distinction separates coordination from informal influence. Informal technical communities can move quickly because entities know one another and solve problems directly. They can also become difficult for outsiders to understand. A board creates a visible institutional point where representation and responsibility can be examined. The public page lists members from different stakeholder positions, which supports the idea that PKIX governance was designed to include more than one organisation.

The secretary designation is evidence of a formal role, not a description of its daily work. Meetings, documents and follow-up may matter to any board, but the public page does not say which of those tasks Ahmed performed. The defensible point is that PKIX attached his name, PTA department and stakeholder representation to a specific board position. Any fuller account would require role descriptions, minutes or other dated records.

For an internet exchange, this administrative layer affects technical outcomes. Entities may need clarity about membership, ports, facilities, operating responsibilities, costs and escalation. They need confidence that one network will not receive hidden control over another. They may need to understand how public agencies, educational networks, commercial operators and technical-community partners relate to one another. Ambiguity can delay connection even when the technical case is strong.

The secretary role is therefore best read as an accountability signal. It says that PKIX presented a board and attached a named person to a specific function within it. That is not proof that the governance model always worked as intended. It is evidence that the exchange effort treated governance as something that required an identifiable structure.

The source boundary also prevents a celebratory shortcut. A title on a public page cannot establish meeting quality, participation rates, conflict resolution or operational reliability. It cannot show whether smaller operators felt heard or whether all decisions were implemented. Those questions require minutes, policies, entity accounts or other records not included here. The responsible conclusion is narrower: Ahmed was publicly identified inside the PKIX governance structure.

A three-city record rather than a single launch

The 2022 APNIC account describes a sequence of PKIX exchange points: Islamabad in 2017, Karachi in 2019 and Lahore later. It says Ahmed assisted with coordination on all three. This makes the record more useful than a one-day launch announcement. A single launch can be ceremonial. A three-location sequence gives evidence of an organisation repeating, adjusting and extending a process.

The sequence does not prove that every exchange had the same governance, membership, traffic or technical configuration. It does suggest that PKIX and its partners confronted similar categories of work more than once: identifying a host, bringing stakeholders together, arranging equipment and software, developing operator capacity, and explaining why participation could be useful. Repetition matters because coordination becomes more valuable when knowledge from one site can reduce uncertainty at the next.

APNIC’s 2022 article attributes to Ahmed the observation that logistics for Lahore were easier than for the previous two exchange points. It also reports that coordination with some new members remained challenging, while PTA had accumulated trust and experience from earlier work. Those are source-attributed statements, not an independent operational audit. They nevertheless reveal the kind of learning the entities wanted to claim: the physical and procedural work could become more familiar, while the human work of addressing concerns remained necessary.

That is a credible pattern for infrastructure institutions. The first deployment forces a group to establish basic relationships and assumptions. The second tests whether the model can travel. The third shows whether the group can use prior experience without assuming that a new local community has identical needs. A coordination role becomes more demanding at each step because the organisation has to distinguish reusable practice from local conditions.

Lahore also involved a different facility context in the APNIC account. The article describes the Lahore exchange as located at the Punjab Information Technology Board, while the earlier exchange points were associated with Higher Education Commission data centres. The source explains this in relation to accessibility and capacity, but this profile does not independently verify facility performance or the full decision process. The important governance point is that host selection was presented as a community concern, not as the private preference of one individual.

Ahmed’s appearance across the three-city account supports a more limited observation about continuity. APNIC identifies him with coordination on all three sites and attributes to him comments about easier logistics and continuing member concerns. The record does not show that he designed the repeated method or personally carried institutional knowledge between sites. PTA, exchange entities, host institutions and technical-community partners all appear in the same accounts.

What the 2020 account says about process

The 2020 APNIC article gives the most detailed public description of the process around PKIX. It says PTA representatives had been facilitating discussions and promoting the exchange since 2015. It attributes to Ahmed an account of bringing stakeholders together, forming working groups and using independent experts to discuss the exchange. The article describes recommendations for an independent board, exchange points in Islamabad, Karachi and Lahore, neutral hosting and affordability for smaller operators.

Those statements should be handled with care. They come from an APNIC editorial account that includes comments attributed to Ahmed and other contextual material. They are useful evidence of the process as publicly described. They are not the same as board minutes, contracts or an independent evaluation of every recommendation. The article also reports traffic and latency outcomes, but those figures are not adopted here as independently verified personal achievements.

The process description is still revealing. It places stakeholder discussion before infrastructure expansion. That order matters. An exchange can be technically available and remain underused if networks do not trust the host, understand the governance or see a manageable path to connection. By contrast, a process that exposes concerns early can shape the location, oversight and cost model before entities commit resources.

The 2020 APNIC account associates Ahmed with facilitation rather than command. Facilitation is sometimes treated as soft work compared with routing or switching. In an exchange environment, it can be a hard dependency. Entities may compete in other parts of the market. They may differ in scale and negotiating power. They may be cautious about sharing operational information. They may worry that a host or dominant operator will gain an advantage. The source does not establish which institutional choices Ahmed personally made; it attributes to him an account of bringing stakeholders together and forming working groups.

The working-group model is significant for the same reason. It distributes technical and governance questions rather than locating them in one office. Independent expertise can help entities test assumptions. Representation from operators, academia, bandwidth providers and public bodies can prevent a narrow design from being mistaken for a common one. The source does not show exactly who attended every group or how disagreements were resolved. It does show that the public rationale for PKIX relied on deliberation.

This is where Ahmed’s PTA affiliation becomes relevant without becoming a claim of control. A regulator can convene organisations that might not otherwise trust one another to set the terms. It can also create concern that a technical exchange is becoming a government instrument. The described board, neutral-location reasoning and stakeholder working groups can be read as safeguards against that concentration. The evidence does not prove that every safeguard was sufficient. It shows that the public design acknowledged the problem.

For leadership analysis, the observable record is facilitation; it is not evidence that Ahmed personally chose between facilitation and direction. APNIC presents his comments in a process that emphasised involvement and trust. That differs from a narrative in which infrastructure is announced and adoption is treated as automatic. The organisational record, rather than an individual decision claim, connects that process to multiple exchange locations over time.

SANOG35 and the discipline of public explanation

The SANOG35 programme lists “Pakistan Internet Exchange Point” by Ahmed Bakhat Masood of PTA. It also lists a second session, on new generic top-level domains, internationalised domain names and the domain-name industry in Pakistan, under “Ahmed Bakht Masood.” The spelling difference matters for identity matching. The shared PTA context supports treating the two spellings as variants, while “Ahmed Bakhat Masood” remains the canonical form used by the PKIX page and other records.

The programme does not reproduce every statement in the presentations, and this profile does not use it to infer claims beyond the listings. Its value is independent confirmation that Ahmed’s role included public technical-community communication. He was not visible only through an institutional directory. He was named as a speaker at a regional network-operator event.

Public explanation is part of operational accountability. An exchange depends on networks understanding what exists, why it is structured as it is and what is expected of entities. A presentation can expose assumptions to people who were not in the original working groups. It can invite questions from operators with experience elsewhere. It can also create a dated record against which later descriptions can be compared.

That does not mean a conference slot proves technical quality. Programmes select speakers for many reasons, and a presentation can be incomplete or promotional. The source does not provide a peer-review verdict. What it proves is visibility: Ahmed was associated publicly with the PKIX update and with PTA at SANOG35.

This visibility matters because coordination work can otherwise become impossible to attribute. When several institutions contribute, later accounts may compress the history into a generic organisational achievement. A programme listing preserves a person-level link without making that person the sole owner of the outcome. It helps answer who was expected to explain the project in that forum.

The second session also hints at a broader public technical role, but the available programme entry does not support turning this article into a domain-name-policy profile. Its title and attribution are enough to confirm the spelling variant and community visibility. Examining the substance of that session would require separate supporting records. Holding that boundary keeps the PKIX article focused on exchange coordination.

For Ahmed, SANOG35 is therefore less a credential than a test of role clarity. The public record placed him in front of an operator community to discuss a specific exchange effort. That supports the view that his work included explanation and convening. It does not establish endorsement by SANOG, APNIC or the audience.

Trust and neutrality as operating requirements

The 2020 APNIC article puts “trust” and “neutrality” in its headline. Those terms can become vague virtues, but the process it describes gives them operational meaning. Trust relates to whether entities believe their concerns will be considered and whether the exchange will be run under known arrangements. Neutrality relates to governance, representation and hosting choices that do not appear to give one commercial entity hidden control.

Ahmed is quoted in the APNIC account describing broad involvement in planning. The article says working groups recommended an independent IXP board with industry representation and neutral hosting. Again, this is a source-attributed process narrative rather than an independent certification. It shows which problems the entities said they were trying to solve.

Neutrality is not achieved by using the word. A facility can be described as neutral while access terms favour some networks. A board can include multiple organisations while decision power remains uneven. A regulator can convene a process while entities still worry about policy influence. The available public records do not supply the contracts, voting rules or participation data needed to resolve all those questions.

The public design nevertheless creates criteria for evaluation. If governance is meant to include different stakeholder groups, observers can ask whether representation remains broad. If hosting is chosen for accessibility, operators can ask whether practical connection conditions match that rationale. If affordability is a goal, smaller networks can compare the stated goal with actual cost and operational burden. The value of a public process is that it turns abstract trust into claims that can be tested.

Different groups in the account had different interests. A technical expert could address switch requirements. A facility operator could address space and access. A network could raise commercial and routing concerns. A public body could bring legal or policy constraints. The sources identify Ahmed with facilitation and coordination, but do not describe which assurances he carried, which decisions he recorded or how the work was divided.

The record calls for restraint in evaluating that participation. Presenting a source-reported latency or traffic improvement as universal would ignore differences among networks and paths. Claiming that one organisation controlled the whole outcome would erase dependencies. The supported statement is that Ahmed appears in a process publicly described through stakeholder involvement, not that his contribution can be ranked against work the sources do not document.

The same restraint should apply to this profile. APNIC reports operational benefits and quotes Ahmed discussing them. Those reports are relevant context, but they are not an audited scorecard of his personal performance. The article can identify documented actions, positions and institutional relationships without turning attributed claims into settled measurements.

Lahore as a test of institutional learning

The Lahore exchange gives the public record a concrete later-stage test. APNIC’s 2022 account describes a third exchange point after Islamabad and Karachi. It says local stakeholders were brought together and that APNIC provided hardware, software and training resources. It attributes to Ahmed the view that logistics were easier because of experience accumulated during the earlier exchange work, while coordination with new members still required attention.

The pattern is instructive. Technical repetition can reduce uncertainty: teams know what equipment categories are needed, what software must be configured and what training has proved useful. Institutional repetition can reduce uncertainty too: entities know that a board exists, that working groups have been used and that particular organisations have supported earlier sites. But neither kind of learning removes local negotiation.

Lahore had its own stakeholders and facility context. A previous agreement in Islamabad or Karachi could not substitute for local confidence. New entities could have different commercial positions, technical resources or concerns about governance. Ahmed’s source-attributed comments recognise that challenge. The role of accumulated trust was not to silence new questions; it was to give the group a history of addressing them.

This suggests an organisational result more durable than a launch event: a coordination method that could be reused. The result should not be overstated as proof that the method was complete or universally accepted. The source does not provide a denominator of operators that declined to join, delayed participation or remained dissatisfied. It does show that PKIX could move from two exchange locations to a third while publicly describing continuity in the convening process.

The involvement of external support also defines a boundary. APNIC’s contribution, as described in its own article, included equipment, software and training. That is relevant to how the Lahore site was assembled. It prevents the story from becoming a claim that Ahmed or PTA independently supplied every capability. It also raises a sustainability question: how much of the operational model depended on outside resources, and how were skills transferred to local operators?

The available record offers a partial answer by emphasising training and capacity development, but not an independent assessment of long-term operating autonomy. Future evidence could include current technical documentation, entity reports, maintenance responsibilities or data about the exchange’s development after launch. Without that material, Lahore is best treated as evidence of an implemented third stage and a repeatable coordination process, not as proof of every claimed benefit.

Ahmed’s place in the account remains consistent. He is a named public coordinator connected to all three sites and to the explanation of what changed in Lahore. That continuity gives the profile its leadership lens. It establishes repeated public association with the work, not personal custody of institutional knowledge or sole responsibility for later deployments.

What PeeringDB can and cannot establish

Two dated PeeringDB API snapshots provide a limited view of PKIX Lahore. The exchange-entity query shows a public exchange entity named PKIX Lahore in Lahore, Pakistan, with the PKIX website. At the capture time, the entity reported net_count as zero. The netixlan query for that exchange identifier returned no rows. Contact and addressing details are irrelevant to the institutional question and are not reproduced here.

These records provide a useful limit. They show that a PKIX Lahore exchange entity existed in the directory at a particular capture time. They do not prove the number of active entities, live ports, traffic, operational health or commercial reach of the exchange. A zero count can reflect the data present in PeeringDB, not necessarily the complete operational reality.

That negative context prevents a common reporting error. A profile could combine APNIC’s launch account with a later directory entity and imply continuing scale without checking what the directory actually shows. The dated snapshots do not support that inference. They require the article to distinguish the historical launch narrative from the later directory record.

The distinction also protects Ahmed from an opposite error. A zero directory count should not be converted into a claim that the exchange was inactive, failed or had no entities. The snapshots establish only what the two API queries returned at the recorded time.

For leadership analysis, this uncertainty matters. Coordinators work in environments where public data is incomplete. Accountability includes saying what a record cannot show. Ahmed’s public role can be established through PKIX, APNIC and SANOG sources even when current exchange-scale evidence remains sparse. The profile should not fill that gap with assumptions.

The redaction decision is equally important. PeeringDB records can contain operational contacts and network details that are not necessary for a public profile. Removing those fields preserves the useful institutional context while avoiding publication of private or sensitive material. It also reinforces that the article is about public responsibility, not about compiling every available data point.

Future reporting could revisit the exchange entity, entity disclosures or other public operational sources. Any change would need a dated capture and the same caution about coverage. For now, the PeeringDB evidence is strongest as a boundary: PKIX Lahore is present as an entity, while active-scale claims remain unverified.

A regulator-linked role without a claim of regulatory command

Ahmed’s PTA affiliation creates both relevance and editorial risk. A regulator can convene market entities and bring public authority to a process. It can also be mistakenly described as controlling technical operations that remain distributed among networks and institutions.

The reference supports a PTA-linked role. APNIC identifies Ahmed with PTA, SANOG35 lists the affiliation, and the PKIX board page places him in regulator or government representation. It does not provide the statutory basis for every PTA action, a complete delegation of powers or proof that Ahmed had unilateral decision authority.

That means the article should separate convening power from operating control. APNIC describes PTA representatives as facilitating discussions and records other organisations in technical, hosting and support roles. Ahmed appears in that distributed record, but the sources do not show that he personally connected every role or controlled the resulting decisions.

This separation is especially important in technical governance. Operators need assurance that routing and interconnection decisions remain technically sound and commercially workable. Public bodies may have policy interests that are broader than the operational needs of an exchange. A credible coordination model has to make those interests discussable without collapsing them into one command structure.

The working-group and board narrative in the APNIC source can be read as an attempt to manage that tension. Multiple stakeholder categories were invited into the design, and an independent board was recommended. The available evidence does not prove perfect independence. It does show that the public rationale recognised the need for representation.

The sources establish Ahmed’s secretary title and presentation record, but do not disclose the work product attached to either. They provide enough to associate him with a formal governance position and public technical communication, not enough to assign documentation, enforcement or operating-control duties.

The leadership standard is therefore procedural. Did the coordination make responsibilities clearer? Did it preserve room for operator concerns? Did it make decisions traceable? The public record offers indicators, not a final evaluation. It is stronger evidence than a generic job title, but weaker than a full institutional audit.

The organisation-level results visible in the record

Several results can be observed without claiming more than the sources show. First, PKIX established a public board page with named representation and a secretary role. Second, the exchange effort was publicly associated with sites in Islamabad, Karachi and Lahore over time. Third, Ahmed’s PKIX work was presented at SANOG35. Fourth, APNIC published two dated accounts that connect him to stakeholder coordination and the later Lahore stage.

These results concern institutional continuity and visibility. They do not establish Ahmed’s private performance review, compensation, promotion history or sole causation. They do show that his name persisted across different kinds of public evidence: an organisation page, a conference programme and external technical-community reporting.

Persistence across sources matters because each source has different limitations. The PKIX page is first-party and good for the stated board role, but not an independent assessment. SANOG35 is good for a programme listing, but not for the truth of every presentation claim. APNIC provides narrative context and attributed comments, but it is also a entity-support organisation describing a project to which it contributed. PeeringDB provides structured exchange context, but not a complete operating census.

The convergence supports a narrow conclusion. Ahmed was a visible PTA-linked coordinator in the PKIX development record, connected to governance and public explanation across multiple exchange stages. No single source has to carry the entire profile.

The organisational result is also visible in the process described. Working groups, a board, neutral-hosting reasoning and entity involvement form a coherent model. The sources do not show whether every part remained unchanged, but the model is more specific than a slogan. It gives future reporting points to verify.

The three-city sequence is the strongest implementation indicator. A process that remained purely conceptual would not produce dated accounts of successive exchange locations. Yet implementation is not the same as verified long-term success. The record supports that the sites were established as described; it does not provide a current independent assessment of each site’s membership, traffic or service quality.

Ahmed’s leadership can be credited at the level of accountable participation. He occupied a role in the governance chain, was publicly identified with coordination and explained the work to an operator community. That is a meaningful organisation-level record even without the hero language often attached to infrastructure projects.

The evidence still missing

The first missing category is current operating scale. The PeeringDB captures do not establish active entity counts, and the APNIC articles are dated. A current public entity roster, technical status page or independently verified measurement would help show how the exchanges developed after the reported launches.

The second is governance detail. The PKIX board page names roles, but the available public sources do not include bylaws, voting rules, meeting minutes, conflict procedures or a complete history of board composition. Those records would allow a stronger assessment of how representation worked in practice.

The third is Ahmed’s exact scope. Public titles and attributed comments establish a relationship to PTA and PKIX. They do not disclose the full boundaries of his authority, the size of any team, reporting lines or which decisions required approval elsewhere. A fuller profile would need dated institutional records rather than inference from senior-sounding language.

The fourth is independent outcome evidence. APNIC’s articles report operational improvements and entity experiences. Because APNIC also supported the exchange effort, those accounts should remain attributed. Independent network measurements, entity case studies or comparative data could test the results without making Ahmed personally responsible for every technical metric.

The fifth is the denominator of non-participation. Public launch stories naturally focus on organisations that joined or supported the project. They do not reveal how many networks declined, what concerns remained unresolved or whether smaller operators faced barriers. That denominator matters when a governance model claims broad accessibility.

The sixth is the later history of the legal and organisational form. The available public sources reviewed here do not establish the exchange organisation’s complete legal history, timing or current status, so this profile does not make a claim about them.

The seventh is continuity of Ahmed’s current role. The PKIX page was captured as a public source, but a page alone may not explain when it was last substantively updated. This article uses the page to establish the published role at capture time, not to infer every present-day responsibility.

These gaps do not invalidate the profile. They define its confidence level. The record is strong enough to describe a public coordination role and a sequence of institutional actions. It is not strong enough for a comprehensive biography or a performance ranking.

Questions for the next stage of reporting

How did the PKIX board divide responsibilities among regulator, operators, academic networks and facility hosts? The answer would clarify whether the governance model translated broad representation into defined authority.

What procedures were reused from Islamabad and Karachi when Lahore was established, and which were changed for local conditions? That would test the source-attributed claim that experience made later logistics easier.

How were concerns from prospective entities recorded and resolved? A documented process would make the trust narrative more measurable.

What current public indicators best represent exchange health without exposing sensitive operational information? Entity counts, route-server status, aggregate traffic ranges or availability reporting might each answer different questions, but any publication would need clear methodology.

How does PTA distinguish its convening role from the operational autonomy of participating networks? That separation is central to confidence in a regulator-linked exchange process.

What responsibilities attach specifically to the Secretary to the IXP Board? A formal role description would make Ahmed’s accountability more precise and reduce the temptation to infer authority from title alone.

How did training and equipment support translate into local operating capacity? The APNIC accounts identify support, but long-term knowledge transfer is a separate result.

What legal and organisational form now governs the exchange effort? The answer would add useful context without inferring present status from older descriptions.

How should the spelling variants in public programmes and organisation records be maintained so that search and attribution remain accurate? Identity hygiene is a small but real part of public accountability.

These questions point toward evidence, not suspicion. They are the natural next checks for an institution whose public case rests on trust, neutrality and repeatable coordination.

Leadership without ownership inflation

Ahmed Bakhat Masood’s public record offers a useful corrective to the way infrastructure leadership is often described. The evidence does not require a founder myth. It does not require a claim that one person built a national system. It shows a named coordinator working through a regulator, an exchange board, stakeholder groups and a regional technical community.

His visible record is procedural but must be described with attribution. APNIC says he assisted coordination across three exchange points and attributes to him an account of stakeholder discussions and working groups. PKIX names him as Secretary to the IXP Board. SANOG lists his PKIX presentation. Those are documented actions and positions; the sources do not show that he personally created the board, chose the hosts or designed the repeated method.

The organisation-level results are similarly bounded. PKIX developed a public board structure, appeared in dated technical-community accounts and extended the exchange record across three cities. Ahmed remained associated with that process through multiple sources. These facts support an assessment of continuity and accountability, not a claim of sole causation.

The constraints define the limits of the conclusion. A regulator affiliation does not prove operating control. A board title does not reveal undocumented duties. A programme listing does not establish the substance or reception of a presentation. A multi-site account does not assign every later result to the person quoted in it. Keeping those limits visible is necessary to preserve the difference between a documented public role and an invented achievement.

PeeringDB’s sparse capture-time data adds a final discipline. It prevents a historical launch account from being converted into an unsupported present-scale claim. Public accountability includes preserving that uncertainty.

The strongest supported conclusion is narrower. Ahmed appears in public records at several points in the PKIX coordination chain: a PTA affiliation, assistance with three-city coordination, a named board position and operator-community presentations. The sources do not assign him personal responsibility for policy, facility selection or every connection among institutions.

The evidence is not complete enough for a sweeping verdict. It is complete enough for a precise one: Ahmed Bakhat Masood has a dated, multi-source public record as a PTA-linked PKIX coordinator, board secretary and community-facing presenter. That record matters because it attaches a named public official to a process described through stakeholder discussion, multiple exchange sites and public technical communication, while leaving outcomes and authority boundaries appropriately attributed.