--- slug: fn-src-email-1659cfb5dda7aacd title: "Brief Notation On Multi-Iterative Forward Hauling of Content For Workload Reduction" kind: source_email status: published hash: d16900b179e49727b4c6d5eddb34bd85476be4ea327aee9e02416540b7d960cb created: 2026-10-11T06:57:24.842Z updated: 2026-10-11T06:57:24.842Z summary: "" tags: [] above: ["[[fn-index-emails]]"] below: [] adjacent: [] nested: [] --- # Brief Notation On Multi-Iterative Forward Hauling of Content For Workload Reduction # Email ## Attachments No attachments. ## Message From: Cyrus Massoumi To: Tom Edwards , Ashley Reis Subject: Brief Notation On Multi-Iterative Forward Hauling of Content For Workload Reduction Sent: Sun, 2 Sep 2018 18:10:42 -0700 Sent (UTC): 2018-09-03T01:10:42.000Z Sent (America/Los_Angeles): 2018-09-02T18:10:42.000-07:00 Account: 62ca724fdabf40deba435e42eb88ef18 Gmail message: 1659cfb5dda7aacd Thread: 1659cf58db10f9c4 Message-ID: CAMG-JC-0y03Yd3pgAnYkNwkuxmrmDKUS5e7VW-vUead+QHBWvg@mail.gmail.com Body coverage: full Body format: markdown ## Body Tom, Wanted to make a notation for something I had mentioned to Maureen, basically a framework for the forward haul of materials & content in the event of successes or failures in production. In the memo I spell out failure events, such as image failure (image causes a failure of a post) ~ a content failure would obviously be when content fails to recoup its cost. Thus the idea of forward hauling. A post goes up and it does not perform well. You can change the title & image, then you are dealing with depreciation. It should be hauled forward. Example: Yesterday McCain was a success. I suggested to Maureen the 10 tweets as a haul forward, the content from the previous post is hauled, the tweets are added, a new post exists. The current iteration is a content remake, but, conceptually: Event The response to the event as a tweet article is the haul forward (re-use images, just add tweets) Then there is the spinning events ~ a person responds to an event, article 3 can encompass event, event + response, or event + subject response. Then another responds, haul forward again. ex: McCain's funeral, McCains Funeral tweet response, McCain's funeral eulogies, Hillary responds, Obama responds. Reduce cost by hauling previous iterations forward, increase depth by hauling forward, reduce image cost by hauling forward, expedite time by hauling forward, ETC. This allows for example, 7 articles instead of 2, in the same way that we have 3 lists where we previously had 1. In practice this could consolidate the gap which exists in organic content efficiency. ## Facts ```json { "platform": "Gmail", "source_id": "1659cfb5dda7aacd", "date_as_recorded": "Sun, 2 Sep 2018 18:10:42 -0700", "from": "Cyrus Massoumi ", "to": "Tom Edwards , Ashley Reis ", "subject": "Brief Notation On Multi-Iterative Forward Hauling of Content For Workload Reduction", "category": null, "body_status": "full text (agent capture)", "account": "massoumi.cyrus@gmail.com", "retrieval": "/home/hatch/workspace/email/gmail/89ebb42d1ae968c07056068775f6becc5a6c3debe9711e02dfd3d3e1c6d8ac4d.md" } ``` --- **above:** [[fn-index-emails]]