Home / Companies / Earthly / Blog / November 2026

November 2026 Summaries

3 posts from Earthly

Filter
Month: Year:
Post Summaries Back to Blog
Engineering guardrails require centralized collection of evidence from source repositories, CI pipelines, tool outputs, and external systems because shared standards such as test coverage are difficult to enforce consistently across varied workflows. The proposed architecture separates evidence collection, normalized revision-scoped posture data, policy evaluation, and feedback delivery, allowing the same policy logic to support AI-assisted development, pull-request checks, deployment gates, dashboards, and investigations. It emphasizes preserving provenance, measurement semantics, component and revision identity, and explicit handling of reruns, missing reports, stale data, collector errors, and differing evidence available at each stage. Effective rollout involves draft evaluations, advisory feedback, canary blocking, time-bound exceptions, versioned policies and collection contracts, operational safeguards, and transparent reporting of unknown as well as passing and failing states. Earthly Lunar is presented as an implementation of this model, offering repository and CI instrumentation, structured evidence collection, policy evaluation, organization-wide visibility, customizable collectors and policies, and more than 300 prebuilt guardrails, while noting that building an equivalent internal system entails ongoing maintenance of parsers, data integrity, and cross-team operations.
Nov 09, 2026 2,333 words in the original blog post.
AI-assisted app-building exercises are increasingly useful only as an initial screen because modern coding models can produce working software without revealing whether a candidate can independently own architecture, make sound trade-offs, or recognize flawed agent decisions. The author argues that effective AI challenges quickly become outdated as models improve, while restrictive workplace AI budgets can limit candidates’ experience with frontier tools and should be distinguished from lack of ability. Live observation of a candidate using AI, including their model choices, delegation habits, pragmatism, and willingness to intervene for specific risks, is presented as more informative than self-reported workflows, while take-home assignments are criticized for favoring candidates with more free time or greater need for a job. As AI-enabled “vibe coding” broadens the applicant pool, the proposed hiring process combines an AI workflow screen with traditional no-AI interviews that assess unfamiliar problem-solving, system-design judgment under changing constraints, and an additional “spark” of exceptional potential demonstrated through impact, progression, persistence, passion, or broader accomplishments. The central aim is to hire engineers who can use AI effectively while retaining responsibility for the systems and decisions it helps create.
Nov 09, 2026 2,050 words in the original blog post.
CVE-2026-98432 is described as a critical Linux kernel vulnerability in IPv4 TCP handling that could allow unauthenticated network-based server compromise, with Multipath TCP cited as one demonstrated attack path, though affected hosts require patching regardless of that feature’s use. The article emphasizes that container image scans cannot confirm remediation because containers share their host’s kernel, so organizations must patch, restart or replace affected servers, and verify the active running kernel against vendor advisories across production and CI environments. It also warns that outdated machine images and infrastructure configuration can repeatedly introduce vulnerable systems, requiring centrally maintained approved image and kernel policies that account for vendor-specific backports. Earthly Lunar is presented as a potential guardrails platform for inventorying infrastructure and build configurations, identifying image selections and self-hosted build machines, and prioritizing services using relevant Go versions, while noting that the proposed CVE-specific checks would need custom implementation. Effective closure additionally requires scheduled verification of live servers, ownership and deadlines for unchecked machines, and confirmation of live patches where applicable.
Nov 02, 2026 1,195 words in the original blog post.