HA-SCOM-003 · Combined records and T01–T14
Template Pack for Source Control Using GitHub
By Henok Ahmed
Version 1.0.0
Document HA-SCOM-003 · First prepared 25 October 2026 · Edited 28 October 2026
Compatible with HA-SCOM-001 and HA-SCOM-002, same edition
Status: Published with author approval on 28 October 2026.
Start with the record you need
Use these records in GitHub issues/PRs or an approved document system. Copy only the relevant record and replace response prompts with actual information. A blank field means incomplete, not approved. Use “not applicable” only with a reason. Reference restricted evidence rather than copying it into an inappropriate repository.
These are text templates, not executable workflow configurations. Foundation may combine records if each decision remains explicit. Controlled must preserve required independent review and production approval. The model defines requirements; these templates implement its records.
Use project-prefixed identifiers such as PROJECT-DEC-001 and stable links. Always record a full commit SHA in actual records; examples in the guide use symbolic labels only. Store artifact checksums with the algorithm and location. Record dates/times with timezone. Keep record revisions attributable. Corrections should preserve the previous decision history.
Choose a record, not a paperwork exercise
This pack is for the same learner as the Operating Model and Practical Guide: a computing graduate beginning informational/marketing website delivery, often working as a freelancer outside Addis Ababa. Use Version 1.0.0 across the family.
A record answers a practical question: what did the client ask for, what changed, what did we check, who actually approved it, and what now runs? Write briefly and clearly. Evidence may be a saved page, diff, observed result, workflow run or a reference to restricted operator records. A sentence saying “tested” does not tell another maintainer what happened.
| Your situation | Start with | What you should be able to explain |
|---|---|---|
| New project | Foundation Project Record below, or T01–T03 | Scope, ownership, profile, source boundary, access and recovery |
| One content/style change | Foundation Change and Delivery Record below, or T04–T09 | Request, diff, actual checks, decisions, target and result |
| Defect, extra request or lesson | T11/T12, linked from the change | Disposition and who will act |
| Missing control or emergency | T10 | Limits, authority, expiry and corrective action |
| Proposal to improve the official model | T13 | Evidence for a general change |
| Henok Ahmed's publication review | T14 | Exact documents and license decision; not a client deployment |
Foundation may combine records; it may not omit applicable controls. Use the fuller template whenever a short field cannot capture the actual issue. Controlled must keep required independent review, production approval and operational evidence explicit. The combined forms do not make a Controlled project eligible for Foundation.
Do not copy a fictional “pass,” SHA or approval into a real record. Use PASS, FAIL or UNTESTED, with evidence and a named verifier. Write “not applicable — reason” only when the criterion genuinely does not apply. Missing data remains unresolved. Keep credentials and private enquiry/customer records out of these forms.
Foundation Project Record — complete once, then update
Combines T01/T02 and references T03. This is a project-specific adaptation record, not a change to the official model. It can live in docs/project-record.md or an equivalent approved location.
A. Purpose and boundaries — T01
- Project name/identifier and mode: practice / client:
- Owner/client and actual decision authority:
- Learner/freelancer and other participants:
- Parent model edition and project adaptation version:
- Audience, visitor action, language and four-page/actual agreed scope:
- Exclusions, agreed revisions and acceptance criteria:
- Client agreement/reference for fee, additional work, service costs and support boundaries:
- Approved public facts, contact disclosure and asset rights:
- Current website, permitted test URL and intended production destination, if applicable:
- Repository owner/URL/visibility, rationale and agreed handover ownership:
- Editing route and authoritative source: files / supported WordPress exports / other:
- How accepted edits move between WordPress and the repository:
- Tracked source/assets and software/documentation/third-party license decisions:
B. Profile and dependencies — T02
- Failure effects, data/privileges, recovery difficulty, dependencies, coordination and obligations:
- Controlled triggers considered; chosen profile and evidence/rationale:
- Uncertainties and investigation owner/date:
- Database, media, editor/theme/plugins, hosting, domain, email/contact service and other dependencies:
- For each relevant dependency: owner, access/data, version/configuration reference, failure effect and verified recovery/fallback:
- Actual power/connectivity/equipment/support constraints and contingency plan:
- Backup/recovery owner, secure reference, applicable method and verification evidence T09:
C. Workflow and responsibility — T01/T03
- Roles, combined duties, self-review disclosure and required independence:
- Branch route, merge strategy and critical branches:
- Checks/manual criteria and actual environment access boundaries:
- Required versus observed enforcement; T03 evidence, gaps and compensation:
- Attributable account access/permissions, review interval and departure/handover plan:
- Evidence/artifact/record locations, access and retention:
- Emergency authority, rollback authority, escalation and deferred-review deadline rule:
- Initial exceptions T10, corrective owners and review/expiry dates:
- Reassessment triggers, next review and deputy/support arrangements:
D. Actual adoption decision — T07
- Decision: accepted / conditional / rejected / deferred:
- Owner/authority, date/time/timezone and evidence:
- Conditions and how fulfillment is checked:
- Authorized next action and exclusions:
Done when: scope, source boundary, ownership, profile, checks and recovery can be explained; adoption is actually accepted for the next work. This decision alone does not authorize production deployment or public launch.
Foundation Change and Delivery Record — repeat per change
Combines applicable T04–T09 and links T10–T12. Use one linked issue/PR/document or a small set of records; avoid duplicate contradictory copies.
A. Request and source — T04/T05
- Record identifier, issue and client-brief reference:
- Problem, intended outcome, included change and explicit exclusions:
- Defect against agreed criteria / new request / learning exercise; scope/price decision if needed:
- Affected pages/URLs, dependencies, data and profile reassessment:
- Acceptance criteria and decision owner:
- Starting source/site baseline and expected current state:
- Base/head branch, final PR and reviewed full commit SHA:
- Diff summary and why the change matters:
- Author self-review, independent reviewer where required, findings/disposition and acceptance evidence:
B. Actual checks and candidate — T06
Use one row per criterion, adding rows as needed. Results begin UNTESTED until someone actually checks them.
| Criterion | Result | Source/version and environment | Verifier and date | Evidence/limits |
|---|---|---|---|---|
| Owner-approved facts and contact disclosure | UNTESTED | [complete] | [complete] | [complete] |
| Links and saved WordPress output | UNTESTED | [complete] | [complete] | [complete] |
| Narrow/wide layout and keyboard checks | UNTESTED | [complete] | [complete] | [complete] |
| Agreed email/phone/form journey, as applicable | UNTESTED | [complete] | [complete] | [complete] |
| Intended public or restricted access | UNTESTED | [complete] | [complete] | [complete] |
| Recovery method appropriate to this change | UNTESTED | [complete] | [complete] | [complete] |
- Candidate/version, exact source, build/dependency details or manual preparation method:
- Artifact/export location and checksum algorithm/value when applicable:
- Relationship between reviewed branch source and merged/candidate source:
- Failed/omitted checks, residual limits, T10 exceptions and T11 feedback disposition:
- Recovery evidence, rejected/superseded candidates and recommendation:
C. Actual decisions — T07
Record each applicable decision, even when they arrive in one message.
| Decision | Actual result and conditions | Approver/authority | Candidate/target | Date and evidence |
|---|---|---|---|---|
| Content/change acceptance | [complete] | [complete] | [complete] | [complete] |
| Release readiness | [complete] | [complete] | [complete] | [complete] |
| Deployment authorization | [complete] | [complete] | [complete] | [complete] |
| Public launch or agreed practice availability | [complete] | [complete] | [complete] | [complete] |
- Decision validity, invalidating changes and condition-verification owner:
- Conditions still unmet; prohibited next actions:
D. Apply and recover — T08/T09
- Exact target URL/environment and page IDs verified for this installation:
- Current-state comparison/drift and resolution before writing:
- Artifact/checksum and relevant configuration verified:
- Backup/recovery reference, operator/deputy, permitted window and rollback triggers/authority:
- Recovery verification/exercise scenario, safe destination, actual result and limits:
- Actual application steps, start/end time with timezone, operator and evidence:
- Result: successful / failed / partial / stopped:
- Post-deployment source, content/contact/access and affected user-journey checks:
- If recovery occurred: trigger, actions, verification and version operating afterward:
- Remaining impact, follow-up owners and owner acceptance:
E. Handover and learning — T08/T11/T12
- Operating version/source and routine editing procedure:
- Owner demonstration of an agreed edit and resulting source reconciliation:
- Repository/service ownership, access/renewals, support limits and recovery contact:
- Outstanding defect or new-request disposition and owners:
- Actual working/learning/waiting time and what informed the next estimate:
- Lesson, evidence, specific improvement, owner/date and follow-up check:
- Final status: IN PROGRESS / BLOCKED / DONE—PRACTICE / DONE—CLIENT:
- Exact unresolved criterion if not complete:
Done when: applicable criteria are met, real decisions match the delivered result, handover is agreed and no material blocker remains. A completed template or an AI-generated summary alone does not satisfy these conditions.
Full reusable templates
The detailed forms below keep the original identifiers so teams can expand a record without changing its references. A first learner need not copy every form into every issue.
T01 Project Adoption Record
Complete before routine delivery. Owner approval establishes adoption, not launch authorization.
- Project name and identifier:
- Purpose, audience, owner, and accountable organization:
- Practice/client mode, agreed scope, revisions and client-brief reference:
- Language, actual connectivity/power/support constraints and contingencies:
- Adopted model edition and project adaptation version:
- Selected profile and link to T02 rationale:
- In-scope source/content/assets:
- Out-of-scope systems and their owners:
- Repository owner, URL, visibility, and rationale:
- Client ownership, access, renewals and repository/service handover arrangements:
- Tracked software/documentation/third-party licensing:
- Branch route and merge strategy:
- Required checks and critical branches:
- Roles: owner, maintainer, contributors, reviewers, release coordinator, operators, deputies:
- Role combinations, self-review disclosure, and independence arrangement:
- Environments, access status, deployment method, and authoritative source:
- WordPress editing/export route, supported source format and drift reconciliation:
- Access review interval and responsible person:
- Evidence/artifact/operational record locations and retention:
- Emergency authority, approval route, recovery authority, and deferred-review deadline rule:
- Initial gaps/exceptions and links:
- Reassessment triggers and next review date:
- Owner decision, conditions, date/time:
- Adoption state: proposed / accepted / superseded:
Completion test: another person can identify responsibilities, workflow, environment boundaries, and outstanding gaps.
T02 Profile and Dependency Assessment
Record consequences and evidence rather than using an unexplained total score.
Profile factors
For each factor, describe exposure, consequence, uncertainty, and evidence:
- Failure or unauthorized-change impact:
- Data sensitivity and production privileges:
- Recovery difficulty, migration, and potential data loss:
- System/organization dependencies:
- Contributor coordination and concurrent delivery:
- Contractual/regulatory/service obligations:
- Controlled triggers that apply:
- Selected profile and rationale:
- Uncertainties and investigation owner/deadline:
- Staffing/tool gaps that must not be mistaken for low risk:
- Owner decision and date:
- Reassessment event/date:
Dependency inventory
Repeat this block for each separately managed dependency.
- Component/service:
- Owner/operator:
- Purpose and upstream/downstream dependencies:
- Data classification/access:
- Environment/configuration references:
- Version/change responsibility:
- Backup/recovery arrangements:
- Failure effect and fallback:
- Evidence and last verified date:
Completion test: profile selection is explainable and external recovery responsibilities are visible.
T03 Control and Access Register
Repeat for each required control; link actual settings and verification.
- Control identifier and requirement:
- Applicable profile/environment/branch:
- Required state:
- Configured state:
- Observed enforcement and verification method:
- Evidence, date, and verifier:
- Status: proposed / configured-unverified / enforced-verified / gap / exception:
- Bypass authority and audit arrangement:
- Gap consequence:
- Compensating action:
- Owner and due date:
- Exception T10, if applicable:
- Review/expiry date:
Access review supplement
- Account/team/app and attributable owner:
- Resource and permission:
- Business need and authorization:
- Last review:
- Retain/change/revoke decision:
- Action evidence and next review:
Completion test: policy is distinguishable from actual enforcement. Do not place credentials in this register.
T04 Change Request
Suitable for an issue. Separate unrelated outcomes.
- Title and owner:
- Problem or opportunity:
- Intended user/operational outcome:
- Scope and exclusions:
- Acceptance criteria expressed as verifiable outcomes:
- Affected users, source, data, dependencies, and environments:
- Impact/profile reassessment required? Reason:
- Validation approach and evidence expected:
- Deployment/recovery implications:
- Dependencies and related issues:
- Milestone and proposed version:
- Priority rationale:
- Included correction versus new scope; client agreement/estimate decision:
- Owner-approved claims, contact disclosure and asset permissions affected:
- Acceptance owner:
- State and decision history:
Completion test: completion can be assessed without guessing what “done” means.
T05 Pull Request and Review
Link T04 and summarize final behavior rather than conversation history.
- Linked change request:
- Base/head branch and reviewed head commit:
- Resulting behavior and rationale:
- Files/components affected:
- Validation performed: check, scope, result, evidence:
- Checks not performed, reasons, and residual consequence:
- Visual evidence where applicable:
- Configuration, data, dependency, security, and license implications:
- Documentation/version updates:
- Deployment/recovery effects:
- Exceptions:
- Author self-review statement:
- Reviewer identity and independence:
- Findings and disposition:
- Review decision, conditions, date:
- Merge strategy and resulting commit:
Explain the diff to a beginner: what should a visitor or maintainer experience differently? Codex-assisted review does not constitute an independent human reviewer.
Checklist:
- Acceptance criteria assessed.
- Evidence corresponds to the reviewed revision.
- Material findings resolved or authorized.
- Required checks/review verified.
- No unnecessary sensitive information included.
Completion test: review applies to the revision actually integrated.
T06 Candidate Validation and Release Record
Use a new candidate identity when source or material artifact changes.
- Project, milestone, candidate version, and stage:
- Exact full source SHA/tag:
- Build tool/dependency versions and workflow/run:
- Artifact location, checksum algorithm/value:
- Build reproducibility or expected variability:
- Scope and linked issues/PRs:
- Test environment/configuration:
- Acceptance criteria: result, evidence, verifier, date:
- Accessibility/content/user-journey checks appropriate to scope:
- Feedback disposition and T11 references:
- Defects, limits, omitted checks, and exceptions:
- Recovery evidence T09:
- Recommended decision: ready / conditional / rejected:
- Rejection reasons or conditions:
- Superseded/succeeding candidate:
- Release notes and approval T07:
- Stable release reference, if subsequently approved:
For each criterion use PASS / FAIL / UNTESTED with actual evidence. Distinguish a GitHub check, a manual observation, client acceptance and an unperformed test.
Completion test: source, artifact, evidence, and decision identify the same candidate. A passing workflow is not represented as complete acceptance.
T07 Decision Gate Record
Repeat for each gate or combine with separately completed decisions.
- Record identifier:
- Gate: adoption / change acceptance / release readiness / deployment authorization / public launch / learning review:
- Project/profile:
- Scope and intended audience/use:
- Exact source/artifact/version where applicable:
- Target environment where applicable:
- Evidence reviewed:
- Known limits and T10 exceptions:
- Decision: approved / conditional / rejected / deferred:
- Conditions and how fulfillment will be verified:
- Approver, role, authority, and independence where required:
- Decision date/time/timezone:
- Validity window:
- Changes/events that invalidate the decision:
- Notification/action owner:
- Later amendments and superseding decision:
Plain-language owner review request
Use as a request, never as a fabricated response:
Please review [candidate/version and preview] for [agreed change].
The intended destination is [actual URL/environment].
The current contact route is [approved route].
Known limits and remaining conditions: [actual details].
Technical evidence/source: [linked record].
Recovery/operator arrangements: [actual reference].
Please state your decision on content, readiness, deployment and public launch
(or restricted practice availability), including any conditions.
No missing decision will be treated as approval.
Copy the actual authorized decision into the record with its evidence. Do not substitute a fictional client response.
Completion test: the next action is authorized for an explicit scope. Silence, meeting attendance, or a green check is not substituted for approval.
T08 Deployment and Verification Record
Complete target/preconditions before writing; complete outcomes afterward.
- Approved T07 and release/artifact T06:
- Artifact checksum verification:
- Destination identity, environment, access status:
- Current deployed version and expected destination state:
- Drift comparison and resolution:
- Configuration/dependency checks:
- Backup references and restoration availability:
- Operator and deployment window:
- Recovery owner, triggers, instructions, and authority:
- Planned user-journey/smoke checks:
- Preconditions satisfied or stop reason:
Execution and result
- Start/end time with timezone:
- Actual artifact/configuration applied:
- Steps/actions and evidence:
- Result: successful / failed / partial / stopped:
- Verification outcomes:
- Rollback triggered? Why and when:
- Recovery actions/evidence:
- Version/configuration operating afterward:
- Outstanding impact and escalation:
- Follow-up issue owners/deadlines:
- Owner acceptance of completion:
Handover supplement
- Operating source/version and agreed deliverables:
- Routine WordPress editing steps and owner demonstration result:
- Repository, domain, host, email and other service ownership/access:
- Renewals, maintenance and support boundaries:
- Recovery contact, instructions and external backup references:
- Final live edits reconciled with repository source:
- Open defects/new requests, owners and dates:
- Owner handover acceptance and evidence:
Completion test: the record shows what actually runs, including after failure; it does not merely repeat the intended release.
T09 Recovery Plan and Exercise
Foundation uses a proportionate verified method; Controlled exercises accepted objectives.
- System/environment and failure scenarios:
- Recovery owner and deputy:
- Acceptable recovery time and data loss, where applicable:
- Owner approval of objectives:
- Recovery artifact, database/media/configuration dependencies:
- Backup references, access, age, and retention:
- Restoration sequence and destination checks:
- Rollback triggers and preauthorized actions:
- Service/data integrity verification:
- Communication/escalation route:
- Constraints and scenarios not covered:
Exercise evidence
- Safe exercise environment:
- Exercise date and participants:
- Scenario and starting state:
- Actions and measured restoration time:
- Data loss/integrity result:
- Objective met? Evidence:
- Findings, assigned corrections, retest:
- Next exercise date or triggering change:
Completion test: source rollback is distinguished from database/media/service recovery. A backup's existence is not presented as a successful restore test.
T10 Exception or Emergency Record
An exception does not transform a missing control into a completed one.
- Requirement/control and affected gate:
- Reason for departure and duration:
- Consequence and obligations:
- Why the requirement cannot currently be met:
- Compensating actions and evidence:
- Permitted/prohibited actions:
- Approver and authority:
- Expiry/review date:
- Owner and corrective issue:
- Monitoring/stop conditions:
- Closure evidence:
Emergency supplement
- Incident and deployed baseline:
- Urgency and authorized emergency route:
- Smallest correction proposed:
- Essential checks and available independent review:
- Recovery authority:
- Deferred checks/review, owner, deadline:
- Development reconciliation and retrospective reference:
Completion test: no nonwaivable obligation is overridden; a bounded decision and correction path exist.
T11 Feedback and Disposition
Record only necessary personal information.
- Feedback identifier/source category:
- Version, environment, date:
- Observed behavior and desired outcome:
- Steps/evidence, appropriately sanitized:
- Classification: defect / improvement / question:
- Impact and priority rationale:
- Decision: accept / reject / defer / needs evidence:
- Reason and decision-maker:
- Linked issue/candidate:
- Owner and target milestone:
- Validation of resolution:
- Communication status through authorized route:
Completion test: feedback has a visible disposition and is tied to the relevant version.
T12 Learning Review
Hold after releases and significant incidents. Assign changes rather than simply listing lessons.
- Release/incident and participants:
- Intended outcome versus observed outcome:
- Evidence and relevant measurement definitions:
- Actual implementation, learning, waiting and correction time:
- Estimate/revision/support lessons, without invented market rates or income claims:
- Connectivity/power interruptions and what the recovery record enabled:
- What worked:
- Failures, rework, escaped defects, unclear decisions:
- Causes supported by evidence:
- Hypotheses needing investigation:
- Recovery and approval effectiveness:
- Improvement: owner, deadline, issue, expected evidence:
- Follow-up verification and result:
- Profile reassessment needed?
- Model proposal T13:
- Review completion decision:
Completion test: unsupported improvement percentages are avoided and actions receive follow-up.
T13 Official Model Change Proposal
Project-specific adaptations should first identify whether a general revision is warranted.
- Proposal identifier and parent edition:
- Problem in existing guidance:
- Evidence from projects/incidents/feedback:
- Proposed wording or structure:
- Affected profiles/templates/examples:
- Tradeoffs and alternative approaches:
- Compatibility and migration implications:
- Proposed patch/minor/major treatment:
- Contributors and acknowledgements:
- Steward decision:
- Approved edition/date:
- Companion alignment and publication action:
Completion test: official changes have an evidence base and adopters can understand migration.
T14 Publication Review and Approval
This record approves the publication family, not any project deployment.
- Author/steward:
- Model, guide, pack identifiers/editions:
- Target learner fit, plain language, executable learning path and competence checks:
- Exact reviewed file hashes or repository commit:
- Content accuracy and profile/gate consistency:
- Fictional example labeling:
- Private/third-party information review:
- License choice, scope, exclusions, and notice:
- Attribution/publication URL:
- Publication format and accessibility review:
- Outstanding changes:
- Decision: approved / conditional / rejected:
- Approver and date:
- Approved publication date/channel:
- Publication verification and edition-history location:
Completion test: publication uses the approved files and activated notice; draft metadata is removed only after approval.
Learner demonstration before offering this service
Perform these on an authorized practice project, then explain them without relying only on an AI response:
- Locate the actual repository, branch, commit and corresponding saved WordPress page.
- Read a focused diff and identify an unrelated or unsupported change.
- Show that an editor-only change is not automatically in Git, and reconcile it.
- Complete a branch/PR cycle with the actual review arrangement disclosed.
- Distinguish a configured automated check from manual acceptance and client approval.
- Reject a candidate when a defined criterion fails; prepare a corrected identity/evidence.
- Demonstrate the applicable recovery method safely and explain what it does not restore.
- Resume after an interruption by inspecting actual state and pending local/remote work.
- Show the real owner/practice-owner decision for the exact permitted destination.
- Hand over editing, source/service ownership, support and recovery instructions.
Evidence location, date and verifier:
Skills not yet demonstrated and next practice action:
These checks demonstrate a bounded exercise, not qualification for every website, guaranteed clients or earnings. Controlled scope still needs suitable people, controls and experience.
Publication package completion checklist
- All three documents share a compatible edition.
- Requirements, cases, and template identifiers agree.
- Real project observations are separated from fictional outcomes.
- License and exclusions are approved.
- No private project records are accidentally included.
- Final publication URL and attribution are inserted.
- Approved source and history are preserved.
- Website publication occurs only after author authorization.
License and edition record
Copyright © 2026 Henok Ahmed. The original educational text, tables, prompts, checklists and text templates in this publication family are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). Give appropriate credit, link to the license and indicate changes, without implying endorsement. This grant excludes underlying project software, private files, third-party materials, trademarks, credentials and personal data. Those materials retain their respective rights.
Source: https://henokahmed.com/source-control-templates/
Edition 1.0.0-draft.4 (28 October 2026) edits the pack for beginning freelance website work, adds combined Foundation records, learner checks, client scope/ownership and handover detail. T01–T14 identifiers are retained from draft.3 for continuity. That draft remained unpublished. Henok Ahmed approved it for publication as Version 1.0.0 on 28 October 2026. Original templates and prompts are unchanged. Publication does not authorize any client deployment or the overall website’s stable public launch.
Publication qualification: instructional prompts have not been validated through a timed learner trial. Fictional examples and results remain illustrative.