> Instead of writing bespoke scripts that operate over GitHub using the GitHub API, you describe the desired behavior in plain language. This is converted into an executable GitHub Actions workflow that runs on GitHub using an agentic "engine" such as Claude Code or Open AI Codex. It's a GitHub Action, but the "source code" is natural language in a markdown file.
This seems like a real headache to me. I understand the value proposition of LLMs in the development cycle, but CI/CD is probably the last place where I want any degree of nondeterminism.
This looks like backwards. I would understand using a LLM to generate a GitHub Actions YAML, but always running your action from a Markdown file seems extremely wasteful in terms of resources.
Edit: ok, looking at example it makes more sense. The idea is to run specific actions that are probably not well automated, like generating and keeping documentation up-to-date. I hope people don't use it to automate things like CI runs though.
This is the ultimate facade of Digital Identity that UIDAI lets happen while sitting idly by. They put a circular against “Aadhaar photocopies not being valid” only to rescind it the next day because everyone made fun of them.
The truth, as you point out, is that Aadhaar in reality is a an “honour based system”, where UIDAI pretends everything is valid and authenticated as long as it gets used everywhere.
I’d love to see a citation for a Hotel being legally allowed access to the Aadhaar KUA system, even before the Supreme Court judgement. No hotel in India does this, because Aadhaar as implemented is a “honor based system” for the majority of usecases where a photocopy of a Aadhaar (with or without QR) is assumed to be valid.
In comparison, a Voter ID and PAN are both hologram protected and forgeries are easily detected.
W3C verifiable credentials do not require a singular identity source, they work perfectly fine with multiple issuers.
Not op,I agree that hotels doesn't do any face matching.
However for getting a new mobile connection the flow is similar to what op has mentioned. It seems one can get a mobile connection by not opting for face recognition, but the process is cumbersome. Similarly for property registrations fingerprints (atleast in some of the states) of the concerned parties is matched against the ones that are associated with their Aadhar.
Yes, because Telcos are designated as AUAs, and expected to do a full KYC under DoT regulations. Hotels are not.
I have two SIMs, and I surprisingly got the newer of them in 20 minutes at a remote village in India without an Aadhaar. Telcos do a Liveness check with their phone instead these days.
I'm not seeing anything very specific in the code - feels like this could be just another Jekyll theme and still work the same. There's some custom front-matter in markdown files, but change that to regular YAML and it will just work.
There is some code for looking up the geo lat/log of locations at compile. not sure how you would do that. But yeah outside of that your are mostly correct.
I used elixir because thats what I know and love so it was mostly just a personal choice rather than a technical one.
> Ensure that the pre-installed Sanchar Saathi application is readily visible and accessible to the end users at the time of first use or device setup and that its functionalities are not disabled or restricted.
Does not sound optional. (I do not have an Aadhaar and have to fight across regulated domains - finance, insurance, banking, investments, even renting).
For others: IFF (Internet Freedom Foundation) was born out of India's SaveTheInternet campaign for Net Neutrality, which helped save India from Facebook's Internet.org. They're currently fighting more than a dozen cases on a variety of matters, but mainly focused on digital rights, censorship, surveillance, and privacy.
Every single Indian SIM holder got dozens of SMS from the regulator to push the app installations. When your marketing campaign is “Notify every Indian SIM holder”, 10M should be expected. Look at the reviews.
RBI pushed an entire new second level TLD to India’s entire banking system with a 6 month deadline. It was a botched rollout but now every bank in India is using .bank.in, despite two of India’s largest bank owning their own TLDs (.hdfc, and .sbi).
It was a very insecure rollout with zero customer awareness, but it happened and almost every large bank moved. Sometimes silly pronouncements do result in silly change.
reply