Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

project template catalog / candidate

Guth Project Templates

Reusable project records with forms, deadlines, workbacks, tools, guides, and qualification gates.

Status: proposal-onlyLifecycle: candidate

Guth Project Templates catalog

Eighteen project archetypes make intake, planning, scheduling, dependencies, evidence, review, and closure explicit.

project templateEngineering buildProposal-only project record for planning and executing a bounded software build from intake through scope, workback, dependencies, evidence, approvals, risk review, and closure. It preserves ownership, deadlines, revisions, and held external effects without implying a connected production backend.project templateApp feature buildA source-bound project record for taking one product capability through intake, scope, ownership, milestones, deadline workback, dependency review, evidence capture, approvals, risk handling, and closure. All implementation and external effects remain proposal-only until separately verified.project templateWebsite surfaceProposal-only project template for planning, governing, evidencing, approving, and closing a public website surface while preserving claim, crawl, accessibility, deadline, and release gates.project templateSecurity remediationA bounded project record and form workflow for investigating, repairing, validating, approving, and closing a security issue without widening authority or implying production effects.project templateIncident responseProposal-only project record for coordinating incident detection, containment, evidence preservation, recovery, approvals, and retrospective work while keeping external effects human-held.project templateApple platform featureProposal-only project record for planning, implementing, qualifying, documenting, approving, and closing a native Apple-platform capability while preserving entitlement, device, evidence, and production-effect boundaries.project templateNative releaseProposal-only project record for preparing an Apple app build for human-reviewed packaging and release decisions, with explicit scope, workback, evidence, approvals, risks, and held external effects.project templateInstrument qualificationProposal-only project record for binding, testing, hardening, documenting, approving, and closing qualification work for one or more Guth instruments without implying provider connection, production state, publication, or customer indexing.project templateField guide buildProposal-only project record and form workflow for creating, testing, maintaining, approving, and closing a source-bound operational field guide with explicit scope, owners, milestones, deadlines, dependencies, workback, evidence, risks, and failure states.project templateResearch studyProposal for a bounded, source-backed research project record with structured intake, scope, milestones, deadlines, dependencies, ownership, workback planning, evidence, approvals, risks, and closure controls. Provider, publication, customer, database, and production effects remain held.project templateExperiment runProposal-only project record for defining an experiment protocol, controls, fixtures, runs, failures, interpretation, evidence, approvals, and closure receipts without implying execution, provider connection, publication, or production state.project templateGrant applicationProposal-only project record for researching, drafting, reviewing, and packaging a grant application without submitting it or implying provider, customer, publication, or production effects.project templateSocial campaignProposal template for planning, drafting, reviewing, scheduling, and measuring a public communications campaign while publication, provider effects, customer indexing, and production state remain human-held.project templateOutreach campaignProposal-only project record for building source-labelled account dossiers and staging outreach for human review without performing an external send.project templateLearning courseProposal-only project record for creating a source-linked learning path with intake, scope, milestones, deadlines, dependencies, owners, workback, tools, guides, evidence, approvals, risks, and closure. Native app surfaces are treated as prototype or indexed routes; provider, credential, database, publication, and production effects remain held.project templateCustomer implementationProposal-only project record and form workflow for configuring a bounded Guth product for a customer while preserving tenant isolation, effect isolation, human review, source provenance, and held production actions.project templateCustomer indexingProposal-only project record for planning a consent-bound customer website crawl and local index while excluding private content and holding all provider, credential, database, customer, publication, and production effects for human review.project templateOperations migrationProposal-only project record and form workflow for moving an operational capability between systems with explicit scope, owners, dependencies, workback deadlines, reconciliation evidence, approvals, rollback readiness, risk controls, and closure.

Lifecycle and authority

These are source-bound candidate operating records generated from observed Guth surfaces and a frozen 926-instrument directory. They are public documentation candidates, not proof of deployment, provider connection, qualification, or authority.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • batch_6a965c417434819092145937de3be9ed
  • batch_6a965db33d78819092ebb3effb90cb6d