An engineering case study of a production low-code workflow on the n8n platform that integrates twelve RSS feeds from five patent offices that identifies five design lessons: P1 (Hybrid Intelligence Architecture), P2 (Format Normalization at Boundaries), P3 (Separation of Content and Presentation), P4 (Graceful Degradation), and P5 (Configuration Externalization), each supported by differentiated within-case evidence.
Abstract
Patent intelligence is hard to automate: data is heterogeneous and multilingual, and monitoring runs on daily cycles. This paper reports an engineering case study of a production low-code workflow on the n8n platform that integrates twelve RSS feeds from five patent offices (EPO, WIPO, USPTO, TIPO, and MOIP). Over a four-month deployment (October 2025 to January 2026; an approximately 120-day window), the system processed 340 items, normalized six timestamp formats, handled English, Chinese, and Korean, and generated three stakeholder-specific output formats with no manual intervention in formatting or delivery. From this deployment, we identify five design lessons: P1 (Hybrid Intelligence Architecture), P2 (Format Normalization at Boundaries), P3 (Separation of Content and Presentation), P4 (Graceful Degradation), and P5 (Configuration Externalization), each supported by differentiated within-case evidence. Output quality was assessed exploratorily with two LLM-based evaluators, whose inter-rater agreement was low for semantic dimensions; a small expert pilot (four English-language items, four raters) provided only a preliminary reference, on which the system output did not exhibit any obvious serious errors. Applying the lessons in other domains is future work, not a contribution. The findings are documented engineering experience from a single production case.
The five-layer approach to using this information asset gives practitioners and researchers a reference architecture for designing, evaluating, and governing enterprise knowledge graph deployments built on proprietary organizational data.
It is argued that AI can function as a discovery and translation layer for dormant technical knowledge, but that such systems must explicitly represent legal uncertainty, data limitations, and commercialization risk.
Sidney Shapiro, Mark Price· arXiv.org· 0 citations
Gold-free, rule-based verification thus locates where MLLM reliability holds, giving human–AI collaboration quantified, disclosed residual risk rather than an implied guarantee, and recommends the extended level where date fidelity is regulatory-critical.
Deploying large language models for AI-driven workflow generation in a production enterprise platform is benchmarked across 29 real-world IT automation scenarios, two generation pipeline architectures, and eight independent runs per prompt-model-pipeline configuration.
Xavier Wrenn, Radoslav Raykov, Aleksandar Angelov et al.· 0 citations
Penetration testing reports are a critical artifact in the cybersecurity workflow, yet their technical complexity frequently limits their utility for non-specialist stakeholders involved in risk remediation decisions. This paper investigates the feasibility of using four open-weight large language models, DeepSeek-r1:3...
Prerit Datta, M. Islam, Ryan Wojciechowski· Annual International Compute...· 0 citations
A rigorous, comprehensive mapping of the ML lifecycle domain between 2015 and 2025 using the PRISMA protocol is provided and a preliminary conceptual layout for an Adaptive Lifecycle Framework (ALF) is introduced, juxtaposing it with legacy paradigms like CRISP-DM.
Ioannis-John Kosmas, T. Papadopoulos, C. Michalakelis· AppliedMath· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.