One job title, in one place

Four files stated who the author is, independently, and they disagreed. Two
called him a deep learning researcher and two an AI/ML engineer; of the two
that agreed on the noun, one listed three fields and the other five. A reader
who landed on the front page, clicked through to the Summa and then looked at
the page source got three answers, and the structured data offered search
engines both titles with no order to them.

Researcher leads now, because that is the strength — including in the
structured data, where the order is not cosmetic. AI/ML engineer stays as a
second title there: it is true, it is searched for, and it is not visible text
claiming to be the headline.

The fix is one editable source rather than one merged sentence. The two fields
do different jobs — the front page wants a stance under a very large name, the
Summa is the title page and can carry the fields — so they keep their lengths
and now share their noun. `getRole()` reads the frontispiece entry, which is
where it can be edited in /admin; ROLE in consts is the fallback when that
entry is missing, and no longer a third opinion. The Vitae had a fourth copy
that listed the fewest fields of any of them; it reads the same source.

Bioinformatics and gene sequence analysis stays in the list, at the author's
word that it is a strength — it was in one variant and missing from two.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: asifuddin01

src/components/home/SummaHead.astro

@@ -2,10 +2,10 @@
 import ArtPlate from '../art/ArtPlate.astro';
 import { getEntry } from 'astro:content';
 import { getHomePlates } from '../../lib/collections';
-import { AUTHOR, LOCATION } from '../../consts';
+import { AUTHOR, LOCATION, ROLE } from '../../consts';
 
 const fp = await getEntry('site', 'frontispiece');
-const role = fp?.data.role ?? '';
+const role = fp?.data.role?.trim() || ROLE;
 const epigraph = fp?.data.epigraph ?? '';
 const attribution = fp?.data.attribution ?? 'the author';
 const location = fp?.data.location ?? LOCATION;

src/components/layout/BaseHead.astro

@@ -1,7 +1,7 @@
 ---
 import { ogPathFor } from '../../lib/og';
-import { SITE, AUTHOR, ROLE } from '../../consts';
-import { getContact } from '../../lib/collections';
+import { SITE, AUTHOR } from '../../consts';
+import { getContact, getRole } from '../../lib/collections';
 
 interface Props {
   title: string;
@@ -28,6 +28,7 @@ const { title, description, image, type = 'website', noindex } = Astro.props;
 const ogPath = image ?? ogPathFor(Astro.url.pathname);
 
 const { github, linkedin } = await getContact();
+const role = await getRole();
 // Astro's pathname keeps a trailing slash; the links and the served URL do
 // not. A canonical that names a different address than the one linked is a
 // canonical pointing at a redirect.
@@ -45,8 +46,10 @@ const personLd = {
    * him only as a researcher after the frontispiece, the meta tags and the
    * title had all moved.
    */
-  jobTitle: ['AI/ML engineer', 'Deep learning researcher'],
-  description: ROLE,
+  /* Both are true and both are searched for, but the order is not cosmetic:
+     the first is what he leads with, and research is the strength. */
+  jobTitle: ['Deep learning researcher', 'AI/ML engineer'],
+  description: role,
   url: SITE,
   sameAs: [github, linkedin],
   address: { '@type': 'PostalAddress', addressLocality: 'Dhaka', addressCountry: 'BD' },

src/consts.ts

@@ -2,8 +2,19 @@
 export const SITE = 'https://asifuddin.com';
 
 export const AUTHOR = 'Md. Asif Uddin';
+/**
+ * The fallback self-description.
+ *
+ * The one that is actually shown comes from the frontispiece entry, which is
+ * editable in /admin; this is what every page falls back to if that entry is
+ * missing. It used to be a third independent copy, and the three disagreed:
+ * two called him a researcher and one an engineer, and the two that agreed on
+ * the noun listed different fields. A reader who moved between the front page,
+ * the Summa and the page source got three answers.
+ */
 export const ROLE =
-  'Deep learning researcher — medical imaging, vision-language models, causal inference';
+  'Deep learning researcher — vision, medical imaging, vision-language models, ' +
+  'causal inference, bioinformatics and gene sequence analysis';
 export const LOCATION = 'Dhaka, Bangladesh';
 export const EMAIL = 'md.asif.uddin@g.bracu.ac.bd';
 export const GITHUB = 'https://github.com/asifuddin01';

src/content/projects/localscholar.mdx

@@ -4,5 +4,7 @@ system: true
 title: "LocalScholar — a private, laptop-scale research assistant"
 summary: "Built because two scoping reviews needed more PDFs than any hosted chatbot would take. Keeps a permanent local library, answers questions across all of it at once, and grounds every claim in a page you can open. Hybrid BM25 and dense retrieval fused by reciprocal rank, then a cross-encoder reranker — an ablation over 30 hand-written questions takes Recall@5 from 0.833 to 0.933 and MRR from 0.672 to 0.840. Refusal is measured too: four questions the library provably cannot answer, four correct refusals. Citations are computed by matching extracted values back against the retrieved passages rather than reported by the model, which took structured extraction from 6/15 fields to 12/15 while making every remaining value more trustworthy. Runs on an 8 GB M1 with no API key and nothing leaving the machine."
 cvSummary: "Local-first RAG research assistant (FastAPI, React, ONNX, Ollama). Hybrid BM25 + dense retrieval with RRF fusion and cross-encoder reranking; measured ablation to Recall@5 0.933, MRR 0.840; verified refusal on unanswerable questions; citations computed from passage overlap rather than self-reported. {localscholar.tests} tests, runs offline on 8 GB."
+link: "https://asifuddin01.github.io/LocalScholar/"
+linkLabel: "See a recorded session"
 repo: "https://github.com/asifuddin01/LocalScholar"
 ---

src/content/site/frontispiece.mdx

@@ -1,7 +1,7 @@
 ---
 title: Frontispiece
-role: Deep Learning Researcher — Vision, Medical Imaging, Vision-Language Models, Causal Inference, Bioinformatics & Gene Sequence Analysis
-tagline: AI and machine learning engineer — I build systems that train, run and can be checked.
+role: Deep learning researcher — vision, medical imaging, vision-language models, causal inference, bioinformatics and gene sequence analysis
+tagline: Deep learning researcher — I build systems that train, run and can be checked.
 epigraph: Correlation is cheap. Only an intervention costs anything.
 attribution: the author
 location: Dhaka, Bangladesh

src/lib/collections.ts

@@ -1,5 +1,5 @@
 import { getCollection, getEntry, type CollectionEntry } from 'astro:content';
-import { EMAIL, GITHUB, LINKEDIN, LOCATION } from '../consts';
+import { EMAIL, GITHUB, LINKEDIN, LOCATION, ROLE } from '../consts';
 import {
   APPARATUS_PARTS, TIER_RULES, COVERAGE_RULES, STRANDS,
   propositionId, type MathTier, type Strand,
@@ -505,6 +505,20 @@ export async function getAxioms(): Promise<CollectionEntry<'axioms'>[]> {
  * Contact details. Editable in /admin under Site text, with the values in
  * consts.ts as a fallback so nothing breaks if the entry is removed.
  */
+/**
+ * How the site describes its author, from the one place that is editable.
+ *
+ * Four files stated this independently and they disagreed — on the job title
+ * in two of them, and on the list of fields in the two that agreed on the
+ * title. Reading it makes the frontispiece entry the source, so it can be
+ * changed in /admin and every page follows, which is the same reason the
+ * contact block below is read rather than repeated.
+ */
+export async function getRole(): Promise<string> {
+  const e = await getEntry('site', 'frontispiece');
+  return e?.data.role?.trim() || ROLE;
+}
+
 export async function getContact(): Promise<{
   email: string;
   github: string;

src/pages/index.astro

@@ -47,7 +47,7 @@ const stack = (await getCollection('instrumentarium'))
 const works = (await getCollection('works')).sort((a, b) => a.data.plate - b.data.plate);
 ---
 <BaseLayout
-  title={`${AUTHOR} — AI/ML engineer`}
+  title={`${AUTHOR} — deep learning researcher`}
   description={tagline}
   folio="I"
 >

src/pages/vitae.astro

@@ -1,4 +1,5 @@
 ---
+import { getRole } from '../lib/collections';
 import { fillFacts } from '../lib/facts.mjs';
 import BaseLayout from '../layouts/BaseLayout.astro';
 import LesionRule from '../components/ornament/LesionRule.astro';
@@ -15,21 +16,22 @@ const skills = (await getCollection('instrumentarium')).sort((a, b) => a.data.or
 const cvMeta = (await getEntry('site', 'cv'))?.data;
 const { email, github, linkedin, location } = await getContact();
 
+
+const role = await getRole();
 ---
 <BaseLayout
   title={`Vitae — ${AUTHOR}`}
-  description={`Curriculum vitae of ${AUTHOR}, deep learning researcher in medical imaging, vision-language models and causal inference.`}
+  description={`Curriculum vitae of ${AUTHOR} — ${role}.`}
   folio="V"
 >
   <div class="codex cv">
     <header class="cv-head">
       <div class="cv-headline">
         <div>
           <h1 class="cv-name" data-press>{AUTHOR}</h1>
-          <p class="cv-role" data-reveal>
-            Deep learning researcher — medical imaging, vision-language models,
-            causal inference
-          </p>
+          {/* Read, not restated. This was a fourth hand-written copy of the
+              same sentence, and it listed fewer fields than the other three. */}
+          <p class="cv-role" data-reveal>{role}</p>
         </div>
         <div class="cv-actions">
           <a class="cv-btn" href="/vitae/cv">Get the PDF</a>