Summary

  • The proposal page identifies AFPUB-2026-GEN-002-DRAFT01 as Under Discussion and embeds an assessment dated 23 June 2026, labelled v1.0 (Initial staff draft), with no previous published assessment. AFRINIC-37 scheduled the relevant PPM session for 15:15–16:05 the next day.
  • The AFRINIC-37 minutes record PDWG Chair Vincent Ngundi saying that day-before provision was unfair to the author, although impact assessments were optional. He proposed defined timelines and a community decision on whether assessments should be mandatory. This is a procedural observation, not evidence of breach, invalidity, prejudice or misconduct.
  • The record establishes document dates, versions, the agenda window, no rough consensus and the later Under Discussion status. It does not establish the public-posting time, usable review hours, readership, private receipt, prejudice or causation.
  • An assessment-to-agenda receipt could bind exact proposal and assessment versions to publication, review, response, decision and correction states without disclosing personal data, confidential legal advice or private deliberation.

The documentary sequence is narrow. The page for the Policy Compliance Dashboard proposal carries the identifier AFPUB-2026-GEN-002-DRAFT01 and the status Under Discussion. Its embedded staff impact assessment identifies the same proposal, bears the date 23 June 2026, calls itself v1.0 (Initial staff draft) and records no previous published assessment.

AFRINIC-37 took place on 24 June 2026 in hybrid online and on-site format. The PPM ran from 09:00 to 17:00 UTC+3. Its agenda placed the Policy Compliance Dashboard at 15:15–16:05. The minutes then record Vincent Ngundi, acting as PDWG Chair, addressing the timing of staff impact assessments. Although such assessments were optional, he said, providing them just a day before was unfair to the author. He proposed that the community define timelines and decide whether impact assessments should be mandatory.

The co-chairs recorded no rough consensus and returned the proposal to the mailing list. The current proposals index, checked on 28 August 2026, still lists AFPUB-2026-GEN-002-DRAFT01 as Under Discussion.

Those entries create a visible sequence, but not a complete review-time record. Six states have to remain separate.

  1. Proposal submitted. The proposal page identifies one exact draft: AFPUB-2026-GEN-002-DRAFT01. This establishes the policy object under discussion, not the timing or completeness of the later staff assessment.

  2. Assessment authored or dated. The embedded assessment is dated 23 June 2026 and marked v1.0 (Initial staff draft). The date is documentary evidence about the assessment itself. It is not, without more, a timestamp for public release.

  3. Assessment publicly available. The proposal page supplies no public-posting timestamp for the embedded assessment. The checked record therefore cannot show the clock time at which the document became available to the author, participants or the wider community.

  4. Author and community able to review. The minutes preserve the Chair’s day-before procedural concern. They do not establish an exact review interval, readership, private receipt, author response time or the degree of scrutiny actually achieved.

  5. Meeting discussion and decision. The agenda establishes a 15:15–16:05 session on 24 June. The minutes establish that the co-chairs found no rough consensus and returned the proposal to the mailing list. They do not attribute that outcome to the assessment’s timing.

  6. Later proposal status. The index still showed Under Discussion on 28 August 2026. That is a later state of the proposal. It is not adoption, ratification, implementation or proof that the June timing issue was resolved.

Consecutive dates can look more precise than they are. The assessment date does not reveal the posting hour, while the agenda gives a scheduled session rather than the exact moment of the co-chairs’ decision. The checked sources therefore do not support an exact review-hour calculation.

The Chair’s word “unfair” must remain in its procedural setting. It records concern about the author’s opportunity to engage before deliberation; it does not make the assessment legally late, prove a breached rule, invalidate the PPM discussion or establish prejudice. His proposed remedy confirms that the underlying questions—whether assessments should be mandatory and when they should appear—were still for the community to define.

An optional document can still shape deliberation by giving participants staff analysis to test against a proposal. The issue here is not its substantive merit, but whether its provenance and review interval are visible. The public materials expose a date-to-agenda sequence while omitting the timestamp and version trail needed to reconstruct actual public availability.

An assessment-to-agenda receipt could supply that missing chain. It would not decide whether the assessment was correct, whether the proposal should advance or whether a particular interval was sufficient. It would identify the exact documents and procedural states on which those judgements were made.

Receipt field Minimum public record Scrutiny gained without exposing protected material
Proposal identity Proposal ID, exact version and cryptographic digest Binds the assessment and meeting record to AFPUB-2026-GEN-002-DRAFT01, rather than to an evolving proposal title
Assessment identity Assessment ID, version, document date, public posting timestamp and digest Separates authorship date from public availability and proves which file was visible
Scope and authority Concise scope statement and responsible AFRINIC function Shows what the assessment covers and who issued it without naming individual staff
Prior-version state None, superseded, withdrawn or earlier published version Prevents “initial” from being confused with a complete public version history
Meeting link Meeting ID, agenda item, scheduled session and recorded decision time Connects the evidence to AFRINIC-37 and the relevant PPM state without disclosing private deliberation
Review rule Applicable minimum interval, or a reasoned public exception Makes timeliness testable while preserving defined flexibility
Revision history Version dates, digests and a concise diff or change note Prevents silent replacement and shows whether later text was available before or after discussion
Author response Public response, no response yet, or response window still open Records opportunity and status without treating silence as agreement or non-reading
Comment handling Comment window and aggregate or itemised public dispositions Shows how review comments were addressed without publishing personal data
Decision and next state Co-chair decision, basis stated at the level already public, and next procedural state Keeps no rough consensus, mailing-list return, Last Call and later states distinct
Correction history Dated correction, withdrawal or supersession note Preserves the original record and explains later changes rather than overwriting them

The receipt’s most important distinction is between the assessment’s date and its public posting timestamp. The first belongs to the document. The second belongs to the public process. A digest would make both useful by identifying the exact file to which the date and timestamp apply.

A minimum review interval would be a community rule, not a fact supplied by the existing record. The minutes show that the Chair proposed defining timelines; they do not show that the PDWG had already adopted one. A reasoned exception field would allow a future rule to remain workable without turning every deviation into an unexplained absence. Publication of the exception could be limited to process grounds and need not reveal confidential legal advice or internal discussion.

The author-response field would record whether a response was published or whether a defined opportunity remained open. It would not claim that the author read the assessment, accepted it or suffered prejudice. Similarly, comment dispositions would show that public observations were answered, deferred or incorporated without exposing private correspondence.

Revision history is essential because an embedded document can otherwise acquire a false sense of permanence. If a later v1.1 or replacement appeared on the same page, readers would need to know whether AFRINIC-37 considered v1.0, a corrected copy or another text. A date alone cannot resolve that question. Digests, public-posting timestamps and concise diffs can.

The receipt would also keep the decision chain honest. “No rough consensus” is a meeting outcome. Return to the mailing list is the next state recorded in the minutes. Under Discussion is the later index status. None of those states proves adoption, rejection, ratification or implementation. Linking them chronologically would reduce the temptation to collapse an unfinished process into a final result.

This is a modest transparency object. It asks for process metadata already capable of being public: identifiers, versions, timestamps, agenda references, response states and corrections. It does not require disclosure of personal data, confidential legal analysis or private deliberation. Its value is not volume but binding. It would let a reader answer a simple question that the present record leaves open: which exact assessment became publicly available, when, for which proposal version, before which decision point, under what review rule, and with what recorded response and next state?

The evidence available today stops earlier. AFRINIC dated the embedded assessment 23 June 2026. AFRINIC-37 discussed the proposal on 24 June. The minutes record a day-before fairness concern and a proposal for future timelines. They do not supply the timestamp needed to convert those facts into an exact review interval. That missing interval is the accountability object.

Sources