One preferred name reused
Name as per Matriculation CertificateAditya Kumar SharmaUnsupported source
Applicant full nameAditya Kumar SharmaPreferred profile value
Neutral baseline: editable values, but no source authority or change history.
Demonstration data
The application safety layer for public recruitment
Give each form the exact detail it asks for.
Your Class X name and your current legal name are both correct. Career ID gives each question the source it asks for, and stops instead of guessing when a record is missing.
Independent hackathon prototype. Not an official government service.
Same citizen · two receiving schemas
Matriculation nameAditya K SharmaClass X Certificate
Applicant full nameAditya Kumar SharmaCurrent legal profile
Both answers are valid. The receiving question determines which source belongs in each field.
Interactive authority replay · Synthetic
One citizen. Two valid names. Two different answers.
Change the evidence and watch the real resolver recompute both receiving fields. It selects only what each reviewed policy supports.
Evidence scenarioTest the system instead of trusting the pitch.
This replay runs the real resolver against a fixed example, on this page only. It does not change the records in the working demo. Whatever you switch here, the citizen journey below still starts from complete evidence — remove a record inside the demo to carry that state through a whole application.
The question selects the source
Defence-style formAditya K SharmaClass X Certificate · 2017-06-04.1
Central-style formAditya Kumar SharmaCareer ID profile record · 8
Every result keeps the receiving policy, source, version, and next action.
Why flat autofill fails
It repeats Aditya Kumar Sharma into both forms. That is an unsupported source for a field asking specifically for the Matriculation record.
Receiving formRequested fieldReviewed policyResolver resultNext action
2 of 2 fields supported. Each value carries its source and policy version.
60/60 labelled regression cases matched0/30 unsupported cases auto-selected0 human participants; no impact claim
Why ordinary reuse fails
Autofill repeats a value. Career ID preserves its meaning.
Flat profileOne preferred valueNo receiving policyWrong-source riskSilent reuse
Authority-aware reuseExact receiving fieldReviewed source policyVisible provenanceSafe refusal
The complete citizen journey
One decision layer, connected to the work around it.
Each credential stays linked to its source. Each eligibility result stays linked to an approved rule. Each application stays linked to the profile version used.
Create once
Build a reusable, source-aware Career ID.
Know before you apply
See every approved rule and why you match.
Only answer what’s new
Reuse the right value from the right credential.
Track everything
Keep each recruitment journey in one place.
AI extracts. Rules evaluate.
Useful intelligence with a clear authority boundary.
AI proposes notification rules once. A reviewer approves them. Deterministic code evaluates every citizen consistently.