Skip to content

0013: Names no document prints, and hidden entries

  • Date: 2026-11-11
  • Status: accepted

Problem

Some of the owner's material must never reach an application: a client under NDA, a former employer they will not name, a side project that is true but does not belong on a resume. Kairos had only --drop and a role profile's drop list. Both apply to one run or one role, and both act after the base resume has been read. So a dropped entry still reached the fact corpus a cover letter is checked against. An evidence story could name the client. A non-entry section (skills, extracurricular) was printed from the base as it stands. Nothing checked a written document for a name.

Kioku's retired resume pipeline solved this in its gathering step (gathering.py at ed10449cb151). Work the owner marked invisible and names no document may print were removed before any model saw the record. A list that could not be read stopped the run instead of being treated as empty. Kairos borrows the idea, not the code.

Options

  1. Where an entry is marked hidden. a. A config list, [documents] hidden_entries, of ### heading substrings. b. A marker on the heading in the base resume file. c. A database flag with a UI toggle.
  2. What happens to input that names a never-print name. a. It is removed before any model sees it, and written text is also checked. b. Only written text is checked.
  3. Matching. a. Whole word, any case. b. Substring, any case.
  4. A written document that still prints a name after its retry. a. It fails closed. b. The sentence is cut.

Choice

The owner chose 1a, 2a, 3a and 4a.

  • Config. [documents] never_print = ["Acme"] and [documents] hidden_entries = ["Wedding site"], both empty by default. A hidden entry is named the way --drop names one: a heading substring in any case. No migration, no parser change. The list survives a re-import of the base resume.
  • Removed at the boundary. kairos.core.documents.exclusions removes, before anything else reads the base resume:
  • every entry that is hidden or whose text names a never-print name, whole;
  • in text without entries (a skills list, a section's opening lines), each line that names one;
  • every evidence story that names one.

A section left with nothing keeps its place with no text, so tailored sections that point at it still resolve, and merge_sections leaves any empty section out. The header (name and contact line) is never cut. kairos.api.services.documents.printable applies this wherever the base resume is read for a document: tailoring, the --preview and kairos roles show entry lists, kairos generate, and both resume exports. So a hidden entry is never listed, scored or sent to a model, and the fact corpus a letter is checked against never holds a removed name. Fit scoring, skills and the candidate profile still read the whole resume, since they print nothing. - Matching. Whole words in any case: "Acme" matches "ACME's", not "Acmesoft". Word edges are checked by hand, so a name that ends in a symbol ("C#") still matches. - Checked on output. A name can still come from the ad or the company, which a letter may repeat. So every written document is checked: - A tailored section fails the never_print rule, is retried once with the name stated, then falls back to its base text, which was already filtered. - A cover letter or criteria response fails check_document the same way, gets one rewrite, then is refused (FactsCheckFailedError). - A resume's merged sections are checked once more before fitting or exporting (ensure_printable). This catches a resume tailored before the name was added, and the error asks the owner to tailor again. That error names the section, not the name, because a run's status is shown in places the owner may share.

The retry turn and the stored validation notes do state the name. The model needs it to remove it, and both stay on the owner's machine. Neither is printed. - Fails closed. The lists are read through load_config. A config that cannot be read raises, so no document is written without them.

Not in scope

  • Rechecking documents written before a name was added. They are checked when written; the owner regenerates them.
  • Filtering repositories or links inside an entry (Kioku's per-repository flag). Kairos entries are Markdown, so hiding the entry or naming the repository covers it.