CV Viva is Henry Rincón's résumé turned into a site you walk through: the career scrolls with you, each role opens its case study with its figures, and the CV comes out as a PDF for applicant tracking systems, from the same source. It is also home to the Portfolio, where every app opens on its brochure, and to “Methods”, nine publications on how design is done.
The career: the line, the big year and the first three rolesThe Vesting case: its thesis, its topics and four figuresProbeta DS end to end: each box says who does it, with its notesMethods: the introduction, nine publications and the first two
Product features: One per function in the user manual that a visitor or the owner sees or uses, matched section by section. The chat's don't count here: they go in its own brochure.Case studies: One for each role in the career, in Spanish and English, counted in the CV's data.Methods publications: The “Methods” files. The site's list counts them from the same folder, so no one types that number.Unit and integration tests: The ones that passed in continuous integration on the last change this version includes. Among other things, they check that the data is well formed, that the case figures are in their document and that Spanish and English say the same; some of them run against a real database.End-to-end tests: End-to-end journeys in a real browser: on desktop, on a phone and in Safari. They are counted by listing them; in the last full run 1257 passed and 59 are skipped on purpose.
studies, one per role, with their figuresmeasured
A static PDF can't show what someone knows how to do. Here each of the nine roles in the career opens its case study with three or four figures, and every figure has to be in its background document. The PDF for applicant tracking systems is still there, from the same source.
For recruiters who have seconds to decide, for technical leads who want to know how someone thinks and not just where they worked, and for whoever comes to see the apps in the Portfolio. A static PDF can't show what someone knows how to do; here every claim leads to its evidence.
It isn't a template or a PDF with animations. All the content lives in validated data: if a field is malformed, if a case's figure doesn't appear in its background document or if a link leads nowhere, the publish stops before it goes out. The site's counts (apps, products, publications) are measured from the content and none is typed by hand. And the site itself is the proof: the Portfolio publishes every app with its process drawn and every figure with its source, without a single access link.
Top to bottom, in the order someone moves through the site: they read the career and open its evidence, explore what gets built and how it is designed, and decide whether to write. On the right, what runs through everything.
One chapter per group: what it solves, when it fits, how it works, its screens and its cards.
A paper CV is read top to bottom and asks you to take every figure on trust. Here the career is something you walk through: a line scrolls with you showing each role's year, the full achievements open with one click and every credential says whether it is earned or in progress.
A single line runs through all nine roles. As you scroll, a circle stays at mid-screen and next to it appears the big year of the role you're reading. With “reduce motion” turned on, everything stays still.
The career: the line, the big year and the first three rolesEach role expands its achievements with figures under “See full achievements”, the same ones the PDF carries. A test requires the same number of achievements in Spanish and in English.
Vesting, with its full achievements expandedTwelve achievements in three rows of four, each with its big number and where it comes from. Two aren't typed by hand: the years of experience are calculated from the start date, and his own AI agents are counted from their published fact sheets.
The twelve achievements in three rows, each with its number and sourceEach certification with its institution and its year, and the ones in preparation with an “In progress” tag instead of a date. Naming a credential in the CV that isn't on the list makes the tests fail.
Five certifications, two marked as in progress instead of a yearNine numbered areas float in a dark rectangle: you can grab them, throw them and, when you pick one, its tools gather around it, joined by a line. “See it all as a list” shows the nine cards. No percentages or proficiency levels.
Skills: the explorer's nine areas at rest, with no percentagesThe three degrees and courses in their own section, with the institution, the period and its logo. The PDF, the printable résumé and the chat read the same information.
The three degrees and courses, with institution and periodWhat is the big year in the career section?
It is the year of the role level with the circle, which stays at mid-screen as you scroll. It comes from each role's period: its first four digits.
Earned certification or in progress?
Both live on the same certifications list, and naming a credential in the CV that isn't on that list makes the tests fail.
It carries its institution and the year it was earned.
It carries an “In progress” tag instead of a date.
Another year of experience goes by: who updates the figure?
No one. The years of experience aren't typed by hand: they are calculated on every publish from the start date, so the figure goes up on its own.
A role has an achievement in Spanish that is missing in English: what happens?
The publish doesn't go out. A test requires the same number of achievements in both languages, and the PDF carries the same ones as the page.
A résumé makes claims and rarely shows them. Here each role opens its case study with its figures, and every figure has to be in its background document. For the recruiting system, the same content comes out as a text PDF.
Each role has its page: the thesis, three or four figures, the context, the challenge, “How I did it” in chapters and what he took away from it. A figure its background document doesn't state stops the publish.
The Vesting case: its thesis, its topics and four figuresThe “CV (PDF)” button delivers a PDF with selectable text, in two columns and in the order an applicant tracking system reads it. It is generated on every publish from the same source as the page, in Spanish and in English.
The printable résumé and its PDF button, from the same sourceWhat does a case study contain?
The thesis in one sentence, a band of three or four figures, the context and the challenge, “How I did it” in chapters, the impact and “What I take with me”. There is one for each role in the career, in Spanish and English.
What is a case's background document?
It is the long, approved text the case page draws from. Every figure in the band has to appear in it, as a number or in words.
The page or the PDF?
Both come from the same data on every publish, so they never say different things: the form changes, not the content.
The case study with its thesis, figures and chapters, to read at leisure.
Selectable text in two columns, in the order an ATS reads it.
A case gets a figure its background document doesn't state: what happens?
The publish stops and names the figure. The live version stays as it was until the figure is fixed or the document backs it.
Telling a project with a link leaves the reader hunting for the evidence. Here every app has its brochure and every agent, dashboard or research piece its technical sheet: what no one else does, its figures with their source, its process drawn and its limits, without a single access link.
Apps, agents, dashboards and research: each front with its box, its status and how many products it has. That count isn't typed: it is measured from the published content.
The Portfolio: four fronts, each with its status and countThe apps come in two blocks, professional first, each in a carousel that shows where it starts and where it ends. You move through it with the arrows, a finger, the keyboard or the trackpad's sideways swipe.
Professional apps in a carousel: two in full and the third peeking inAll ten apps open on their brochure, at a single address per app: the app's card in the Portfolio says “View brochure” and old links arrive in a single hop. At the foot, “Where it stands” gives the pinned version, and the neighbors lead to the previous or the next app without going back to the apps list.
At the foot of HackGuard's brochure: where it stands and its two neighborsIn each app's brochure, “End to end” draws the whole process: each box says who does it, the decision is marked where it is made and the loops stay in plain sight. The sheets of agents, dashboards and research pieces that have a process draw it in BPMN, one lane per actor. Both come from the data, and a malformed process stops the publish.
Probeta DS end to end: each box says who does it, with its notesEach app has its brochure: the promise with its figures and screens, a chapter per feature group, the end-to-end process, the figures with their source and, at the close, “Use it”. It has contents, a search box, an app tour of the screens, and it prints.
HackGuard's brochure: the promise, its screen and the five sectionsThe pieces that aren't apps have their two-minute technical sheet: the headline of what no one else does, its figures with their source, its limits and what it never does. Those that bring data add “What the data says”: each finding with its figure and its source.
Energy and climate: six findings, each with its figure and sourceA private app can show its static simulation: “See the simulation →”, in “Use it”, opens its page, where it plays in a frame or full screen and doesn't load until someone asks for it.
planlang's simulation, opened in a frame inside its pageWhat is an app's brochure?
Each app's page: it opens with the promise, its figures and its screens, walks through its features chapter by chapter and closes with “Use it”. Agents, dashboards and research pieces have a two-minute technical sheet instead.
What do “measured” and “declared” mean next to a figure?
It is its source. Measured comes from a counter or a command; calculated, from a measurement with a rate or a rule; declared was set by a person; estimate is inferred. A figure with no source doesn't get in.
An app or an agent?
An app is shown in its brochure; an agent, a dashboard or a research piece, in its technical sheet. What changes is how much each product brings and whether it can be requested.
Its brochure draws the process end to end and closes with “Use it”: the waiting list, with no promised date, and the roadmap to vote on.
Its two-minute technical sheet; with data, it adds “What the data says”. It is shown, not handed over.
An app arrives with a process that has no end, or a decision with a single path: what happens?
The publish fails and the error says what and where. The diagram comes from the data, so a malformed process never gets drawn.
Visitors don't just read: they vote on what's next for each app with one click, propose an idea, join the waiting list or write. None of it requires an account, and the messages travel to the owner's inbox without being stored in any database.
In “Use it”, each app shows what it has planned and lets you vote with one click, no sign-up; five ideas are shown and “See all N ideas” shows the rest. The count comes from the database at that moment; if the database doesn't respond, the section says so and turns off the buttons.
Dash Agent's roadmap in “Use it”: three ideas to vote on, no votes yetBelow the roadmap, a box takes ideas in the visitor's own words, with an optional email. The proposal reaches the owner's inbox and is neither published nor stored in the database.
The box to propose a feature for Dash AgentIn “Use it”, the close of each app's brochure, a form signs up whoever wants in, with the app already chosen and no promised date; it is also at the foot of the apps list. Only the apps have one: agents, research and dashboards are shown, not handed over.
The waitlist in “Use it”, with the app already chosen and no promised dateThe contact form asks for a name, an email, an optional reason (a project, an advisory, a training, a talk or a role) and the message, and delivers it to the owner's inbox. It has a per-visitor limit and a trap for bots.
The contact form: name, email, reason and messageWhat does a vote store?
Only the app, the feature and the date: neither the IP nor the identity of whoever votes. The “you already voted” notice lives in the visitor's browser.
Waiting list or “Write to me”?
Both reach the owner's inbox and neither is stored in a database. Agents, research and dashboards have no waiting list: they are shown, not handed over.
Only on apps, in “Use it”, the close of their brochure, with the app already chosen and no promised date.
The general form: name, email, an optional reason and the message.
Someone clears their browser data and votes again: does it count?
Yes: voting counts one vote per browser. It is the price of asking for no sign-up and storing no personal data, and it is stated as a limit.
Someone sends “Write to me” and the email service isn't configured: what happens?
The sender sees the confirmation, but the message doesn't arrive. Since the form stores nothing, no copy is left: it is one of the stated limits.
A CV says where someone worked, not how they design. “Methods” publishes it: nine long pieces on how AI, data and BI systems are designed, with the same ten blocks, the evidence kept apart from judgment and dated sources.
“Methods” gathers nine long publications, each on a “How … should be …” question about AI, data or BI. The list counts its pieces from the files: no total is typed by hand.
Methods: the introduction, nine publications and the first twoEvery publication has the same ten blocks, with an index and an anchor per block. The evidence from projects, the state of the field and the author's judgment are labeled with a symbol, a word and a color, never with color alone.
The three labeled voices and the index of the ten blocksEvery publication has its map: a diagram with real text, which can be selected and translated, and below it a node-by-node reading, for screen readers and for print.
The map of an agent system, with its shape legendWhat are the three voices?
Evidence (●): what was done in a named project, drawn only from the site's corpus. State of the field (◆): what the field does, from a source with title, publisher, date and link. Judgment (▲): the author's position, labeled as such. Each carries a symbol, a word and a color, never color alone.
What are the ten blocks?
The problem, the map, the phases, the design decisions, what is new in 2026, the failure modes, the metrics and controls, the evidence from projects, the limits and scope, and the sources with their review date. Always in that order, each with its anchor.
The map or its reading?
Both say the same: the diagram to see it, the reading for whoever can't see it or prints it.
A diagram drawn from the data, with real text you can select and translate.
The same map in words, node by node, for screen readers and for print.
A state-of-the-field claim arrives without a source: what happens?
The publish stops and names the file and the field. Each voice carries only its own evidence: the field, its dated source; the evidence, its document; the judgment, none.
The details that make a site trustworthy are looked after too: everything exists in Spanish and English, the menu fits in four destinations, an address that doesn't exist returns a 404 that makes sense, motion can be turned off and a mistyped field stops the publish without breaking what is already live.
The header carries the HR mark, four destinations (Résumé, Portfolio, Methods and Contact), the PDF résumé and the language. On a phone, the same menu opens with a button and closes with Escape.
The phone menu: the HR mark and the four destinationsOne variable puts the whole site into “I'm fine-tuning my site”, in the visitor's language and with the PDF résumé in both languages. It returns 503 with “come back later”, so search engines don't replace the site.
Under maintenance: the notice and the PDF résumé in both languagesA file that doesn't exist returns a 404, not a server error, with a page in Spanish and in English and a button to each home page.
The 404 in Spanish and English, with a button to each home pageThe whole site exists in Spanish and in English. Switching language keeps you at the same reading point, even though the English is shorter, and the root always opens in Spanish.
It runs through the whole app.Sections reveal themselves as you scroll, with counters and the timeline in motion. With “reduce motion” turned on in the system, all the content appears still.
It runs through the whole app.All the content lives in data files in Spanish and in English: editing and publishing updates the website, the PDF and the chat at once. A malformed field stops the publish and the live page doesn't break.
It runs through the whole app.What is the content gate?
All the content lives in data files, in Spanish and English, validated on every publish. A malformed field stops the publish and names the file; the live page doesn't break. Editing and publishing updates the website, the PDF and the chat at once.
Maintenance or 404?
One is a deliberate pause; the other, a page that isn't there. Neither leaves the visitor without a way out.
The whole site says “I'm fine-tuning my site”, with the PDF résumé in both languages, and returns 503 so search engines come back later.
An address that doesn't exist returns 404, not a server error, with a button to each home page.
You switch to English halfway through the career: where do you land?
At the same reading point: the role you were reading stays at the same height, even though the English text is shorter.
You turn on “reduce motion” in your system: what changes?
Sections stop revealing themselves as you scroll, and the counters and the timeline stay still: all the content appears at once.
The whole path. No swimlanes: every box says who does it, and the ones with the screen icon show it.
Every figure says where it comes from. And what the app does not do is spelled out too.
One per function in the user manual that a visitor or the owner sees or uses, matched section by section. The chat's don't count here: they go in its own brochure.
One for each role in the career, in Spanish and English, counted in the CV's data.
The “Methods” files. The site's list counts them from the same folder, so no one types that number.
The ones that passed in continuous integration on the last change this version includes. Among other things, they check that the data is well formed, that the case figures are in their document and that Spanish and English say the same; some of them run against a real database.
End-to-end journeys in a real browser: on desktop, on a phone and in Safari. They are counted by listing them; in the last full run 1257 passed and 59 are skipped on purpose.
The site's page templates, counted in its files at the pinned version: a single one serves, for example, all nine case studies. They include the maintenance page, the 404 and each app's entry, which is its brochure: a single one for all twelve.
The architecture and product decisions written down and numbered in the repository, 1 to 30 in this version.
Spanish and English, each at its own addresses, with the content in two mirror files. A test requires them to say the same.
Declared by the owner: hosting runs on a free plan and email on its service's free plan, at 100 a day. The custom domain is not included.
