Building a Government Reference Architecture Doc

“Building a Government Reference Architecture Doc” is the search phrase. The file needs a decision. A P5 GovTech Founder who cannot attach a dated packet-capture or proxy log should not schedule another workshop. This guide is the decision, the artefact, and the stop rule — written for Indian government, PSU and campus buyers, not for a global CIO newsletter.

Founders lose government deals on clocks, not on models. GeM is a marketplace with categories, incident flags and payment cycles. GFR 2017 still frames propriety. A Proprietary Article Certificate, when it is lawful, lives in Rule 166 — not Rule 161. DPIIT recognition can relax some formalities where a notice writes the relaxation. It is not a technical score.

We will not invent a circular, a GMV, or a percentage so the heading looks like research. Where the title bank dangles a figure, we treat it as a hook to interrogate. Where the law is silent, we say so. Confirm everything against the live Gazette, the live GeM term, and counsel. This is not legal, procurement or engineering advice.

What is actually true — and what the heading is hiding

Take the heading literally. “Building a Government Reference Architecture Doc” is either a control you can show a stranger, or it is decoration. Decoration is how a state transport department ends up with a public agent, an undeclared tool, and a noting that says “AI-enabled.”

A free pilot that touches personal data is a processing activity you may not have a schedule for, and a commercial trap that trains the buyer to expect unpaid production. Price a time-boxed object with a stop rule, a data pack you brought, and a deletion certificate. Then say no if the object is a hostage demo on live Aadhaar-linked rows.

The primary keyword “reference architecture document” is useful for search. It is useless in a file unless you define the object, the owner, the artefact and the revisit. Those four fields are the whole article, restated for this title.

PSU buyers are not “slow startups.” They have vigilance, unions, board notes and, in some sectors, a regulator who can ask for the log. University buyers have syndicates and exam calendars. State departments have transfers. Map the decision maker and the file owner separately. The person who liked your demo is often neither.

• Define reference architecture document in one sentence a stranger can score.
• Name a designation, not a vendor, as owner of “Building a Government Reference Architecture Doc.”
• Attach a dated packet-capture or proxy log or write the date it will exist.
• Name the instrument. Do not name a mood.

How to score “Building a Government Reference Architecture Doc” in a note, not in a slide.

Claim in the deck	What the file needs	Fail if missing
We handle reference architecture document	Named owner (the CIO) plus a dated packet-capture or proxy log	A heading with no attachment
a state transport department is ready	A dated readiness note with a stop rule	A photograph of a workshop
Compliant / sovereign / secure	The instrument: DPDP schedule, CERT-In mapping, GFR clause, or guideline paragraph	An adjective without a PDF date
Pilot succeeded	Held-out task, baseline, and a kill sentence	A newspaper line

How this fails in a real Indian file

The common failure is a photograph. Someone ran a demo titled Building a Government Reference Architecture Doc, used a live row because “otherwise it will not impress,” and left no pack, no deletion, and no owner. Six months later the question is not “did the model work.” The question is “who has the log.”

Do not publish a government case study that names a scheme, a citizen, or a live URL unless the buyer’s counsel said you may. “Building in public” is a marketing habit. A noting is not a tweet. Confidentiality clauses survive your LinkedIn calendar.

The second failure is a transferred champion. Indian postings are not a risk register line you add for colour. If reference architecture document lives in one officer’s inbox, it will die in that inbox. Write a deputy. Write a zip. Write a runbook a stranger can run.

The third failure is mixing legal persons. NIC is not NICSI. IndiaAI compute access is not an application empanelment. A GeM catalogue is not a PAC. A guideline is not a Gazette. Mixing them is how you apply to the wrong portal and then blog that the state is hostile.

• Workshop photograph, no artefact.
• Champion posted out, no deputy, no zip.
• Live personal data in a demo, no schedule.
• Guideline sold as statute, or a forecast sold as a measurement.
• Wrong legal person: NIC / NICSI / IndiaAI / GeM / PAC mixed on one slide.

How to run “Building a Government Reference Architecture Doc” as a four-week object

Start with a sentence a secretary can repeat: what reference architecture document is, what it is not, and what you will attach. Then collect a dated packet-capture or proxy log. If you cannot collect it this week, write the date you will, and do not demo until that date.

Cash collected is not GMV. A GeM order is not money in the account. Bid/no-bid is a runway decision. If you cannot name the payment clock, the EMD, and the person who signs the CRAC, you are not selling — you are volunteering.

Keep personal data off the demo path. Use a pack you brought. Write training and improvement rights as refused unless counsel says otherwise. If the buyer insists on live data, insist on a processing schedule and a deletion certificate, or walk.

Put CERT-In-relevant logs in India for the required period if the object is in scope of the 2022 directions. Put DPDP roles on a one-page schedule. Do not claim localisation the Act does not write.

A playbook is a sequence with owners. “reference architecture document” as a workshop title is not a playbook. The weeks below assume a single department or a single PSU unit, not a national programme.

If a week produces no artefact, cancel the next week. That is the whole discipline.

1. Week 0: write the sentence you want in the file. If you cannot write it, you are not ready to meet.
2. Week 1: collect the live notice, the current DPA/schedule draft, and the data-classification note. Screenshot dates.
3. Week 2: run the object on a non-production pack. Minute what broke.
4. Week 3: put the artefact in the note and name the owner after the next transfer.
5. Week 4: schedule the revisit. Put the calendar invite in the file, not in a chat.

What to put in the next note

Next note, three dated sentences: (1) we mean reference architecture document as [definition]; (2) the owner is [designation] with deputy [designation]; (3) the artefact is [name] last checked on [date], next check on [date]. If you cannot write the three sentences, you are not ready to buy or to sell.

Attach a dated packet-capture or proxy log or a one-page reason it does not exist. Refuse a vendor one-pager as the only annexure. A P5 GovTech Founder signs the note. The vendor does not.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

We do not have time for another control

You already have a control: the day someone asks why a citizen got the wrong answer. “Building a Government Reference Architecture Doc” is that day, scheduled. A two-page note now is cheaper than a six-month reconstruction later.

The vendor said this is included

Included in a brochure is not included in a statement of work. Ask for the artefact that would exist if reference architecture document were true. If they cannot name it, it is not included.

This is only a pilot

A pilot that touches personal data, a public URL, or a write tool is a production-shaped object with a short calendar. DPDP duties and CERT-In clocks do not wait for your go-live banner. Time-box it, use a pack you brought, and write the deletion.

A field playbook for “Building a Government Reference Architecture Doc”

Run this as a month, not as a mindset. If a week produces no artefact, stop. A state transport department does not need another group photograph.

1. Write the one-sentence definition of reference architecture document that a secretary can repeat.
2. Assign the CIO as the file owner. Put a deputy on the same line for the next posting order.
3. Collect a dated packet-capture or proxy log or write why it does not yet exist and when it will.
4. Map the data path for one user-visible answer: prompt, retrieval, tool, log, exit.
5. Name the instrument: DPDP schedule, CERT-In 2022 mapping, GFR clause, GeM term, or guideline paragraph.
6. Run one non-production rehearsal. Minute what broke. Do not use live citizen rows.
7. Put a stop rule and a revisit date in the note. Create the calendar invite.
8. Tell the vendor, in writing, which hops and which training rights are refused.

How this shows up in the file

If this article does its job, someone will put “Building a Government Reference Architecture Doc” on a change-advisory or a bid-opening agenda as a single line with an owner. That is the success metric. Traffic is not.

Revisit when the model, the SI, the GeM term, the region, or the posting order changes. Unsigned watch items are souvenirs.

This article is informational, not legal, procurement or engineering advice. Confirm against the current Gazette, circular, GeM term and your counsel before you file it.