essays: 2 older ports + 1 original — Vault 2019, Enable & Connect 2019, TYPO3 AI stack - #4
Merged
Conversation
Three new pieces in one PR: essays/introducing-our-vault-service-2019.md en · 2019-02 · ~570 words · status: historical · topics: secrets-management / infrastructure / architecture-decisions. Port of the 2019 HashiCorp Vault adoption write-up. Stripped 4 internal links (Google Slides deck, 3 Confluence wiki cross- links to internal Vault/Concourse/Ansible setup pages) plus internal Vault UI URL plus 'TA1/TA2' team-area names plus 'blugento shop factory' internal product name. Top banner sets Stand: 2019 expectation and forward-references nr-vault as the later TYPO3-native chapter. Six years on, it pairs naturally with the new TYPO3 AI stack essay below. essays/enable-connect-it-principles-2019.md en · 2019 · ~195 words · status: current · topics: engineering- leadership / it-principles / team-enablement. Short principles note: 'IT exists to enable teams to help themselves'. Stripped one internal IT-overview link and two 'Netresearch' company- name mentions; kept the conversational 'Hi all!' voice and the public urbandictionary tl;dr link. Status: current — the principles are stated as enduring and align with the 2024 yearly motto 'Enable, Connect & Innovate'. essays/typo3-ai-stack-vault-llm-cowriter.md de · 2026-05 · ~1,720 words · status: current · topics: typo3 / ai-assisted-development / architecture / secrets-management / open-source-maintainership. Brand-new original essay (NOT a Confluence port). Argues that the three Netresearch TYPO3 AI extensions (nr-vault, nr-llm, t3x-cowriter) are best understood as a layered stack built bottom-up — secrets first, then shared LLM infra, then the visible feature. Cites 6 specific ADRs in nr-llm by number with deep-links: ADR-001 (Provider Abstraction), ADR-012 (API key encryption — superseded), ADR-021 (Provider Fallback Chain), ADR-023 (Backend Capability Permissions), ADR-025 (Per-User AI Budgets), ADR-026 (Provider Middleware Pipeline). Closing argument ties back to the 'resilient structures' / 'reduce implicit dependencies' thread that runs through the rest of engineering-notes. Note on Why rebase? (2017): the fourth post in this batch failed. The Confluence page is a single image (a screenshot of git log --graph showing a tangled merge mess from a 'wagento/...' Magento- theme repo) with NO body text. The screenshot itself contains a third-party vendor name, external developer first names, internal ticket numbers, and an internal hostname — none safely republishable. Either drop the post or rewrite from scratch with a clean synthetic example; that's a separate decision. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three new pieces in one PR — two ports of older Confluence posts and one brand-new original essay tying together the three Netresearch TYPO3 AI extensions.
introducing-our-vault-service-2019.mdenable-connect-it-principles-2019.mdtypo3-ai-stack-vault-llm-cowriter.mdVault 2019 (port)
The 2019 HashiCorp Vault adoption write-up, restored from the internal wiki. Stripped: a Google Slides deck link, three internal Confluence cross-links (Concourse-Vault, Ansible-Docker-Vault setup pages), an internal Vault UI URL, "TA1/TA2" team-area names, "blugento shop factory" product name. Top banner sets Stand: 2019 expectation and forward-references the new
nr-vaultextension as the next chapter — six years on, this and the new TYPO3 AI stack essay below pair naturally.Enable & Connect 2019 (port)
Short principles note (~195 words). Stripped one internal IT-overview link, two "Netresearch" company-name mentions; kept the conversational "Hi all!" voice and the public urbandictionary tl;dr link. Status: current — the principles are stated as enduring and align with the 2024 yearly motto "Enable, Connect & Innovate".
TYPO3 AI stack (original — first non-port essay)
Brand-new ~1,720-word essay drafted by sub-agent, structured as the suggested vault → llm → cowriter layered narrative. Cites 6 specific ADRs in
nr-llmby number with deep-links:Closing argument ties back to the "resilient structures / reduce implicit dependencies" thread that runs through the rest of engineering-notes.
Voice caveat: this is the first essay drafted by a sub-agent (not a port + edit pass). The agent flagged it as "v1, may want voice pass". The technical claims are sourced verbatim from the three READMEs and the ADR files; the framing and lede are the agent's. If a stand-alone voice revision feels needed before promotion, easy to follow up.
Why rebase? — fourth port did not happen
The Confluence page (id 79074403) is a single image — a
git log --graphscreenshot showing a tangled merge mess from awagento/...Magento-theme repo. No body text. The screenshot itself contains a third-party vendor name, external developer first names, internal ticket numbers, and an internal hostname — none of which is safely republishable as-is. Either we drop it or rewrite as a fresh post with a clean synthetic example; flagging for a separate decision.