import type { Metadata } from "next"; import { ActionAnchor, ActionLink, InfoPanel, PanelGrid, RouteHero, RouteShell, StatusLabel } from "@/components/visual-system"; import { fitAssessment } from "@/content/knowledge-pages"; const title = "Should We Use Day Shift? | Day Shift"; const description = "Strong-fit, weak-fit, and decision questions for choosing a proportionate repository-native coding-agent workflow."; export const metadata: Metadata = { title: { absolute: title }, description, alternates: { canonical: "/fit" }, openGraph: { type: "website", title, description, url: "/fit", siteName: "Day Shift" }, twitter: { card: "summary_large_image", title, description }, }; function AssessmentList({ items }: { items: readonly string[] }) { return ( ); } export default function FitPage() { return (
See the workflow Review commercial terms
Strong fit

Continuity and evidence matter

Weak fit

The records cost more than reconstruction

    {fitAssessment.decisionQuestions.map((question, index) => (
  1. {index + 1}.{question}
  2. ))}

Boundary

Day Shift complements coding assistants, Git, pull requests, issue trackers, code review, and CI. It does not replace them or force arbitrary external agents to follow policy.

Choose a workflow Read known limitations
); }