{"plans":[{"id":9,"plan_id":"social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-1b76e8cf","pack_name":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","start_date":"2026-11-20","posting_time":"08:00","timezone":"Australia/Sydney","item_count":12,"artifact_dir":"/var/lib/bada/exports/bada-bing-social-calendar-social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-1b76e8cf","external_publish_performed":false,"target_app_write_performed":false,"human_review_required":true,"created_at":"2026-11-19T01:34:12.307936+00:00","receipt_hash":"6dfcaf35a012cadc4fa96a870de818ed6b872cc9962090675db1ecefe9dd4986","customer_id":"amtl","archived":false,"archive_note":"","source_artifact":"","schedule":[{"item_id":"li-data-care-01","day_index":1,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-20","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 1","working_angle":"","content_format":"linkedin_image_post","body_text":"Every business has one spreadsheet that runs everything.\n\nNobody remembers who built it. Three people have their own copy. The newest version is called FINAL_v7_REAL.xlsx, probably.\n\nHere is the part we find interesting: nobody ever decided that file would become load-bearing. It just did, one quiet week at a time.\n\nThe risk is not the spreadsheet. Spreadsheets are wonderful tools. The risk is the silence around it: no owner, no backup plan, no one who can say what breaks if it is wrong.\n\nField audits of operational spreadsheets keep finding the same thing: most of the ones auditors open contain at least one error.\n\nWhich spreadsheet would hurt most if it was wrong this week?","sources":[{"label":"audit claim source","url":"https://panko.com/ssr/Audits.html"}],"assets":[{"filename":"li-card-01.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source for the audit claim: https://panko.com/ssr/Audits.html Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-02","day_index":2,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-24","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 2","working_angle":"","content_format":"linkedin_image_post","body_text":"A customer rings to question a quote.\n\nSales opens the CRM: one address. Accounts opens the invoicing tool: another. Marketing's list has a third, plus a first name spelled two ways.\n\nNobody in this story made a mistake. The business simply never picked which system wins when they disagree.\n\nSo the answer to \"which one is right?\" becomes whoever checked last. That is not a data strategy. That is a coin flip with a polite voice.\n\nThe fix is not a big migration project. It starts smaller: know where the same record lives twice, and decide, once, who owns the winner.\n\nHow many systems in your business think they own the customer record?","sources":[],"assets":[{"filename":"li-card-02.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-03","day_index":3,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-26","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 3","working_angle":"","content_format":"linkedin_image_post","body_text":"Every owner we meet locks the office at night and knows exactly where the keys are.\n\nAsk the same owner where the customer details sit, and the honest answer is usually a wave: \"in the system somewhere.\"\n\nSomewhere is inboxes. Somewhere is an export on a laptop from March. Somewhere is the shared drive folder called Old Stuff.\n\nThis is not carelessness. It is what happens when data grows faster than anyone's map of it.\n\nThe first step in protecting sensitive information is unglamorous: knowing where it is. A map before a lock.\n\nIf a customer asked tonight where their details are stored, how long would an honest answer take?","sources":[],"assets":[{"filename":"li-card-03.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Australia's breach statistics, for context: https://www.oaic.gov.au/privacy/notifiable-data-breaches/notifiable-data-breach-statistics-dashboard Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-04","day_index":4,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-30","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 4","working_angle":"","content_format":"linkedin_image_post","body_text":"Picture the most common data breach in Australia.\n\nIt is not a hooded figure in a dark room. It is a normal Tuesday. Someone is flat out, autocomplete grabs the wrong name, and a spreadsheet of customer details goes to a stranger.\n\nFrom that moment a clock starts. Australian privacy law gives a business up to 30 days to assess whether the mistake is serious enough to report, and the OAIC expects you to show your working.\n\nThink about what that assessment needs: what was in the file, whose details, where else the file lived, who else got it.\n\nMost businesses would be answering those questions for the first time, during the worst week of their year.\n\nThe businesses that cope are the ones that already had the answers written down.","sources":[],"assets":[{"filename":"li-card-04.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Current breach statistics and trends: https://www.oaic.gov.au/news/media-centre/data-breach-notifications-increase-to-all-time-high-in-2025,-new-ndb-stats-show Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-05","day_index":5,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-02","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 5","working_angle":"","content_format":"linkedin_image_post","body_text":"Nine words: \"Show me everything you hold about me.\"\n\nA customer can ask that, in Australia, today, by email, for free. And behind that one sentence is a treasure hunt: the CRM, the invoicing tool, the support inbox, the marketing list, the spreadsheets, the backups.\n\nFor a well-run business it is an afternoon. For most it is a fortnight of archaeology, and the honest answer is still \"we think that is everything.\"\n\nWe keep coming back to the same thought: the question is simple, so the answer should be simple too. It only gets hard when the records were never kept with that question in mind.\n\nIf that email arrived tomorrow morning, who in your business would own the reply?","sources":[],"assets":[{"filename":"li-card-05.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-06","day_index":6,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-04","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 6","working_angle":"","content_format":"linkedin_image_post","body_text":"Somewhere in your business this week, someone pasted real work into an AI tool to save an hour.\n\nA customer email to summarise. A quote to tidy. A spreadsheet to explain.\n\nThat is not disobedience. It is initiative, and it is exactly what you hired for. The gap is that nobody wrote down which tools, with what data, on whose say-so.\n\nIBM's 2026 breach study found one in four malicious breaches are now AI-enabled. The tools are not the enemy. The blank page where the register should be is.\n\nA one-page list, kept current, beats a policy nobody reads: what is allowed, what never goes in, who approves a new tool.\n\nCould you say, right now, which AI tools your business used this week?","sources":[{"label":"audit claim source","url":"https://newsroom.ibm.com/2026-07-29-ibm-study-one-in-four-malicious-breaches-are-ai-enabled,-costing-companies-6-million-on-average"}],"assets":[{"filename":"li-card-06.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source: https://newsroom.ibm.com/2026-07-29-ibm-study-one-in-four-malicious-breaches-are-ai-enabled,-costing-companies-6-million-on-average Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-07","day_index":7,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-08","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 7","working_angle":"","content_format":"linkedin_image_post","body_text":"When someone leaves, there is a checklist. Laptop back, accounts off, card returned, farewell lunch.\n\nHere is what the checklist misses: the map in their head.\n\nThey knew which export was current. Which folder was the real one. Why the third column in that sheet is never to be touched. Six months later, nobody can reconstruct it.\n\nWe think of this as the quietest data risk in small business. Not theft, not malice. Just knowledge that walked out politely on a Friday.\n\nHandover usually means \"show the new person the ropes.\" It should also mean: the records explain themselves without the old person in the room.\n\nIf your most experienced person left next Friday, what would nobody be able to find by Wednesday?","sources":[],"assets":[{"filename":"li-card-07.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-08","day_index":8,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-10","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 8","working_angle":"","content_format":"linkedin_image_post","body_text":"Something changed in the last few years and many owners felt it first at renewal time.\n\nThe insurer, the auditor, the tender form: they stopped accepting \"we take data security seriously\" as an answer. Now they ask for proof. What data do you hold. Where. Who can see it. When did you last check.\n\nGood intentions do not export as a PDF.\n\nThis is actually reasonable of them. A promise is a mood; a record is a fact. The businesses that sail through these requests are not bigger or richer. They simply kept receipts as they went.\n\nThe question worth asking this quarter: if someone said \"show me\" on Monday, would you be proud of what you hand over by Friday?","sources":[],"assets":[{"filename":"li-card-08.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-09","day_index":9,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-14","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 9","working_angle":"","content_format":"linkedin_image_post","body_text":"Bad data never sends you an invoice. It bills you anyway.\n\nIt bills in the quote rebuilt because the price list was stale. The order re-sent to the old address. The report redone because two exports disagreed and someone had to find out why.\n\nGartner puts the average cost of poor data quality at US$12.9 million a year per organisation. For a small business the number is smaller, but the shape is the same: quiet hours of rework that nobody quotes for and nobody claims back.\n\nThe frustrating part is that these hours are already paid. They just buy nothing new.\n\nWhere did your team's rework hours go last month?","sources":[{"label":"audit claim source","url":"https://www.gartner.com/en/data-analytics/topics/data-quality"}],"assets":[{"filename":"li-card-09.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source for the Gartner figure: https://www.gartner.com/en/data-analytics/topics/data-quality Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-10","day_index":10,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-16","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 10","working_angle":"","content_format":"linkedin_image_post","body_text":"Here is a test we like.\n\nImagine a new starter on their first morning. No training, no handover, just one question on a sticky note: \"Is our data OK today?\"\n\nIn most businesses, that question travels. It goes to the person who \"knows the systems\", waits for them to finish a call, and comes back as a shrug with a story attached.\n\nWhen the answer to a basic question needs one specific human, the system is the human. That works, until they are on leave, or on a plane, or gone.\n\nThe goal is boring and wonderful: a business where anyone can get a plain answer in a minute, in words, without disturbing anyone.\n\nWould your business pass the new-starter test today?","sources":[],"assets":[{"filename":"li-card-10.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-11","day_index":11,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-18","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 11","working_angle":"","content_format":"linkedin_image_post","body_text":"A customer says no to marketing on a phone call. Everyone hears it. Everyone agrees.\n\nWhere does that no live?\n\nIn too many businesses it lives in the memory of whoever took the call, next to the login for the old router and the alarm code from 2019. Six months later a campaign goes out, the customer is on the list, and the business genuinely believed it had done the right thing.\n\n\"I think we removed them\" is not a record. Consent needs what any promise needs: what was agreed, who agreed it, when, and where it is used.\n\nThe businesses that get this right treat a customer's no with the same care as a signed contract. Because it is one.\n\nWhen did you last check that your lists and your promises still match?","sources":[],"assets":[{"filename":"li-card-11.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-12","day_index":12,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-22","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 12","working_angle":"","content_format":"linkedin_image_post","body_text":"Bookkeeping used to be a dreaded annual shoebox. Then it became a habit: a little, often, and tax time stopped being a mystery.\n\nData care is at the same turning point.\n\nNone of the problems in this series need a transformation program. They need a rhythm: know what you have, check it briefly, fix the small things while they are small, keep the receipt.\n\nFive minutes a month beats a panic a year. A plain answer beats a perfect one that arrives too late.\n\nWe have spent these posts on the shape of the problem, because we think most businesses already recognise it in their own week.\n\nNext, we will show you what we built about it.","sources":[],"assets":[{"filename":"li-card-12.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"filtered_item_count":12,"spark_packet":{"plan_id":"social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-1b76e8cf","content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","platform":"LinkedIn","date_range":{"start":"2026-11-20","end":"2026-12-22"},"domain_mix":["data care"],"post_count":12,"boost_candidates":[],"cta":"Review organic performance first; paid boost requires explicit approval.","landing_page_need":"Review whether an AMTL page or offer exists before any paid action.","budget_state":"approval_required","external_publish_performed":false,"paid_action_performed":false,"human_review_required":true},"ripple_packet":{"plan_id":"social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-1b76e8cf","content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","platform":"LinkedIn","expected_lead_type":"Business owner, founder, operator, or technology decision-maker interested in practical AI adoption.","cta":"Ask what workflow, risk, or decision they want AI to make easier.","likely_questions":["How would this apply to my business?","What can be automated safely?","How do I prove AI output is reliable?"],"follow_up_angle":"Offer a practical review conversation, not a hard sell.","buying_intent_posts":[{"item_id":"li-data-care-01","day_index":1,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-20","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 1","working_angle":"","content_format":"linkedin_image_post","body_text":"Every business has one spreadsheet that runs everything.\n\nNobody remembers who built it. Three people have their own copy. The newest version is called FINAL_v7_REAL.xlsx, probably.\n\nHere is the part we find interesting: nobody ever decided that file would become load-bearing. It just did, one quiet week at a time.\n\nThe risk is not the spreadsheet. Spreadsheets are wonderful tools. The risk is the silence around it: no owner, no backup plan, no one who can say what breaks if it is wrong.\n\nField audits of operational spreadsheets keep finding the same thing: most of the ones auditors open contain at least one error.\n\nWhich spreadsheet would hurt most if it was wrong this week?","sources":[{"label":"audit claim source","url":"https://panko.com/ssr/Audits.html"}],"assets":[{"filename":"li-card-01.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source for the audit claim: https://panko.com/ssr/Audits.html Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-02","day_index":2,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-24","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 2","working_angle":"","content_format":"linkedin_image_post","body_text":"A customer rings to question a quote.\n\nSales opens the CRM: one address. Accounts opens the invoicing tool: another. Marketing's list has a third, plus a first name spelled two ways.\n\nNobody in this story made a mistake. The business simply never picked which system wins when they disagree.\n\nSo the answer to \"which one is right?\" becomes whoever checked last. That is not a data strategy. That is a coin flip with a polite voice.\n\nThe fix is not a big migration project. It starts smaller: know where the same record lives twice, and decide, once, who owns the winner.\n\nHow many systems in your business think they own the customer record?","sources":[],"assets":[{"filename":"li-card-02.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-03","day_index":3,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-26","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 3","working_angle":"","content_format":"linkedin_image_post","body_text":"Every owner we meet locks the office at night and knows exactly where the keys are.\n\nAsk the same owner where the customer details sit, and the honest answer is usually a wave: \"in the system somewhere.\"\n\nSomewhere is inboxes. Somewhere is an export on a laptop from March. Somewhere is the shared drive folder called Old Stuff.\n\nThis is not carelessness. It is what happens when data grows faster than anyone's map of it.\n\nThe first step in protecting sensitive information is unglamorous: knowing where it is. A map before a lock.\n\nIf a customer asked tonight where their details are stored, how long would an honest answer take?","sources":[],"assets":[{"filename":"li-card-03.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Australia's breach statistics, for context: https://www.oaic.gov.au/privacy/notifiable-data-breaches/notifiable-data-breach-statistics-dashboard Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-04","day_index":4,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-30","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 4","working_angle":"","content_format":"linkedin_image_post","body_text":"Picture the most common data breach in Australia.\n\nIt is not a hooded figure in a dark room. It is a normal Tuesday. Someone is flat out, autocomplete grabs the wrong name, and a spreadsheet of customer details goes to a stranger.\n\nFrom that moment a clock starts. Australian privacy law gives a business up to 30 days to assess whether the mistake is serious enough to report, and the OAIC expects you to show your working.\n\nThink about what that assessment needs: what was in the file, whose details, where else the file lived, who else got it.\n\nMost businesses would be answering those questions for the first time, during the worst week of their year.\n\nThe businesses that cope are the ones that already had the answers written down.","sources":[],"assets":[{"filename":"li-card-04.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Current breach statistics and trends: https://www.oaic.gov.au/news/media-centre/data-breach-notifications-increase-to-all-time-high-in-2025,-new-ndb-stats-show Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-05","day_index":5,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-02","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 5","working_angle":"","content_format":"linkedin_image_post","body_text":"Nine words: \"Show me everything you hold about me.\"\n\nA customer can ask that, in Australia, today, by email, for free. And behind that one sentence is a treasure hunt: the CRM, the invoicing tool, the support inbox, the marketing list, the spreadsheets, the backups.\n\nFor a well-run business it is an afternoon. For most it is a fortnight of archaeology, and the honest answer is still \"we think that is everything.\"\n\nWe keep coming back to the same thought: the question is simple, so the answer should be simple too. It only gets hard when the records were never kept with that question in mind.\n\nIf that email arrived tomorrow morning, who in your business would own the reply?","sources":[],"assets":[{"filename":"li-card-05.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"approved_for_manual_posting","approval_evidence_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA==","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approved per operator-supplied record"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"crm_customer_write_performed":false,"external_send_performed":false,"human_review_required":true}},{"id":8,"plan_id":"social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-0e08aea6","pack_name":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","start_date":"2026-11-20","posting_time":"08:00","timezone":"Australia/Sydney","item_count":12,"artifact_dir":"/var/lib/bada/exports/bada-bing-social-calendar-social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-0e08aea6","external_publish_performed":false,"target_app_write_performed":false,"human_review_required":true,"created_at":"2026-11-19T01:33:33.520803+00:00","receipt_hash":"06dde6e7cfbf3b1808dd3e6e74bd799d6271298449d9b38557846d8828a0b201","customer_id":"amtl","archived":false,"archive_note":"","source_artifact":"","schedule":[{"item_id":"li-data-care-01","day_index":1,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-20","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 1","working_angle":"","content_format":"linkedin_image_post","body_text":"Every business has one spreadsheet that runs everything.\n\nNobody remembers who built it. Three people have their own copy. The newest version is called FINAL_v7_REAL.xlsx, probably.\n\nHere is the part we find interesting: nobody ever decided that file would become load-bearing. It just did, one quiet week at a time.\n\nThe risk is not the spreadsheet. Spreadsheets are wonderful tools. The risk is the silence around it: no owner, no backup plan, no one who can say what breaks if it is wrong.\n\nField audits of operational spreadsheets keep finding the same thing: most of the ones auditors open contain at least one error.\n\nWhich spreadsheet would hurt most if it was wrong this week?","sources":[{"label":"audit claim source","url":"https://panko.com/ssr/Audits.html"}],"assets":[{"filename":"li-card-01.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source for the audit claim: https://panko.com/ssr/Audits.html Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.124313+00:00"},{"item_id":"li-data-care-02","day_index":2,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-24","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 2","working_angle":"","content_format":"linkedin_image_post","body_text":"A customer rings to question a quote.\n\nSales opens the CRM: one address. Accounts opens the invoicing tool: another. Marketing's list has a third, plus a first name spelled two ways.\n\nNobody in this story made a mistake. The business simply never picked which system wins when they disagree.\n\nSo the answer to \"which one is right?\" becomes whoever checked last. That is not a data strategy. That is a coin flip with a polite voice.\n\nThe fix is not a big migration project. It starts smaller: know where the same record lives twice, and decide, once, who owns the winner.\n\nHow many systems in your business think they own the customer record?","sources":[],"assets":[{"filename":"li-card-02.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.154359+00:00"},{"item_id":"li-data-care-03","day_index":3,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-26","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 3","working_angle":"","content_format":"linkedin_image_post","body_text":"Every owner we meet locks the office at night and knows exactly where the keys are.\n\nAsk the same owner where the customer details sit, and the honest answer is usually a wave: \"in the system somewhere.\"\n\nSomewhere is inboxes. Somewhere is an export on a laptop from March. Somewhere is the shared drive folder called Old Stuff.\n\nThis is not carelessness. It is what happens when data grows faster than anyone's map of it.\n\nThe first step in protecting sensitive information is unglamorous: knowing where it is. A map before a lock.\n\nIf a customer asked tonight where their details are stored, how long would an honest answer take?","sources":[],"assets":[{"filename":"li-card-03.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Australia's breach statistics, for context: https://www.oaic.gov.au/privacy/notifiable-data-breaches/notifiable-data-breach-statistics-dashboard Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.179568+00:00"},{"item_id":"li-data-care-04","day_index":4,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-30","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 4","working_angle":"","content_format":"linkedin_image_post","body_text":"Picture the most common data breach in Australia.\n\nIt is not a hooded figure in a dark room. It is a normal Tuesday. Someone is flat out, autocomplete grabs the wrong name, and a spreadsheet of customer details goes to a stranger.\n\nFrom that moment a clock starts. Australian privacy law gives a business up to 30 days to assess whether the mistake is serious enough to report, and the OAIC expects you to show your working.\n\nThink about what that assessment needs: what was in the file, whose details, where else the file lived, who else got it.\n\nMost businesses would be answering those questions for the first time, during the worst week of their year.\n\nThe businesses that cope are the ones that already had the answers written down.","sources":[],"assets":[{"filename":"li-card-04.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Current breach statistics and trends: https://www.oaic.gov.au/news/media-centre/data-breach-notifications-increase-to-all-time-high-in-2025,-new-ndb-stats-show Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.202136+00:00"},{"item_id":"li-data-care-05","day_index":5,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-02","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 5","working_angle":"","content_format":"linkedin_image_post","body_text":"Nine words: \"Show me everything you hold about me.\"\n\nA customer can ask that, in Australia, today, by email, for free. And behind that one sentence is a treasure hunt: the CRM, the invoicing tool, the support inbox, the marketing list, the spreadsheets, the backups.\n\nFor a well-run business it is an afternoon. For most it is a fortnight of archaeology, and the honest answer is still \"we think that is everything.\"\n\nWe keep coming back to the same thought: the question is simple, so the answer should be simple too. It only gets hard when the records were never kept with that question in mind.\n\nIf that email arrived tomorrow morning, who in your business would own the reply?","sources":[],"assets":[{"filename":"li-card-05.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.224777+00:00"},{"item_id":"li-data-care-06","day_index":6,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-04","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 6","working_angle":"","content_format":"linkedin_image_post","body_text":"Somewhere in your business this week, someone pasted real work into an AI tool to save an hour.\n\nA customer email to summarise. A quote to tidy. A spreadsheet to explain.\n\nThat is not disobedience. It is initiative, and it is exactly what you hired for. The gap is that nobody wrote down which tools, with what data, on whose say-so.\n\nIBM's 2026 breach study found one in four malicious breaches are now AI-enabled. The tools are not the enemy. The blank page where the register should be is.\n\nA one-page list, kept current, beats a policy nobody reads: what is allowed, what never goes in, who approves a new tool.\n\nCould you say, right now, which AI tools your business used this week?","sources":[{"label":"audit claim source","url":"https://newsroom.ibm.com/2026-07-29-ibm-study-one-in-four-malicious-breaches-are-ai-enabled,-costing-companies-6-million-on-average"}],"assets":[{"filename":"li-card-06.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source: https://newsroom.ibm.com/2026-07-29-ibm-study-one-in-four-malicious-breaches-are-ai-enabled,-costing-companies-6-million-on-average Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.246464+00:00"},{"item_id":"li-data-care-07","day_index":7,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-08","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 7","working_angle":"","content_format":"linkedin_image_post","body_text":"When someone leaves, there is a checklist. Laptop back, accounts off, card returned, farewell lunch.\n\nHere is what the checklist misses: the map in their head.\n\nThey knew which export was current. Which folder was the real one. Why the third column in that sheet is never to be touched. Six months later, nobody can reconstruct it.\n\nWe think of this as the quietest data risk in small business. Not theft, not malice. Just knowledge that walked out politely on a Friday.\n\nHandover usually means \"show the new person the ropes.\" It should also mean: the records explain themselves without the old person in the room.\n\nIf your most experienced person left next Friday, what would nobody be able to find by Wednesday?","sources":[],"assets":[{"filename":"li-card-07.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.267001+00:00"},{"item_id":"li-data-care-08","day_index":8,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-10","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 8","working_angle":"","content_format":"linkedin_image_post","body_text":"Something changed in the last few years and many owners felt it first at renewal time.\n\nThe insurer, the auditor, the tender form: they stopped accepting \"we take data security seriously\" as an answer. Now they ask for proof. What data do you hold. Where. Who can see it. When did you last check.\n\nGood intentions do not export as a PDF.\n\nThis is actually reasonable of them. A promise is a mood; a record is a fact. The businesses that sail through these requests are not bigger or richer. They simply kept receipts as they went.\n\nThe question worth asking this quarter: if someone said \"show me\" on Monday, would you be proud of what you hand over by Friday?","sources":[],"assets":[{"filename":"li-card-08.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.288194+00:00"},{"item_id":"li-data-care-09","day_index":9,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-14","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 9","working_angle":"","content_format":"linkedin_image_post","body_text":"Bad data never sends you an invoice. It bills you anyway.\n\nIt bills in the quote rebuilt because the price list was stale. The order re-sent to the old address. The report redone because two exports disagreed and someone had to find out why.\n\nGartner puts the average cost of poor data quality at US$12.9 million a year per organisation. For a small business the number is smaller, but the shape is the same: quiet hours of rework that nobody quotes for and nobody claims back.\n\nThe frustrating part is that these hours are already paid. They just buy nothing new.\n\nWhere did your team's rework hours go last month?","sources":[{"label":"audit claim source","url":"https://www.gartner.com/en/data-analytics/topics/data-quality"}],"assets":[{"filename":"li-card-09.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source for the Gartner figure: https://www.gartner.com/en/data-analytics/topics/data-quality Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.311625+00:00"},{"item_id":"li-data-care-10","day_index":10,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-16","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 10","working_angle":"","content_format":"linkedin_image_post","body_text":"Here is a test we like.\n\nImagine a new starter on their first morning. No training, no handover, just one question on a sticky note: \"Is our data OK today?\"\n\nIn most businesses, that question travels. It goes to the person who \"knows the systems\", waits for them to finish a call, and comes back as a shrug with a story attached.\n\nWhen the answer to a basic question needs one specific human, the system is the human. That works, until they are on leave, or on a plane, or gone.\n\nThe goal is boring and wonderful: a business where anyone can get a plain answer in a minute, in words, without disturbing anyone.\n\nWould your business pass the new-starter test today?","sources":[],"assets":[{"filename":"li-card-10.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.334689+00:00"},{"item_id":"li-data-care-11","day_index":11,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-18","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 11","working_angle":"","content_format":"linkedin_image_post","body_text":"A customer says no to marketing on a phone call. Everyone hears it. Everyone agrees.\n\nWhere does that no live?\n\nIn too many businesses it lives in the memory of whoever took the call, next to the login for the old router and the alarm code from 2019. Six months later a campaign goes out, the customer is on the list, and the business genuinely believed it had done the right thing.\n\n\"I think we removed them\" is not a record. Consent needs what any promise needs: what was agreed, who agreed it, when, and where it is used.\n\nThe businesses that get this right treat a customer's no with the same care as a signed contract. Because it is one.\n\nWhen did you last check that your lists and your promises still match?","sources":[],"assets":[{"filename":"li-card-11.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.357709+00:00"},{"item_id":"li-data-care-12","day_index":12,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-22","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 12","working_angle":"","content_format":"linkedin_image_post","body_text":"Bookkeeping used to be a dreaded annual shoebox. Then it became a habit: a little, often, and tax time stopped being a mystery.\n\nData care is at the same turning point.\n\nNone of the problems in this series need a transformation program. They need a rhythm: know what you have, check it briefly, fix the small things while they are small, keep the receipt.\n\nFive minutes a month beats a panic a year. A plain answer beats a perfect one that arrives too late.\n\nWe have spent these posts on the shape of the problem, because we think most businesses already recognise it in their own week.\n\nNext, we will show you what we built about it.","sources":[],"assets":[{"filename":"li-card-12.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"held_for_later","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"held_no_external_action","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true,"last_receipt_note":"Duplicate import from registry-permission miss; superseded by plan suffix 1b76e8cf. Held, not deleted. No platform action.","last_receipt_at":"2026-11-19T01:34:52.381917+00:00"}],"filtered_item_count":12,"spark_packet":{"plan_id":"social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-0e08aea6","content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","platform":"LinkedIn","date_range":{"start":"2026-11-20","end":"2026-12-22"},"domain_mix":["data care"],"post_count":12,"boost_candidates":[],"cta":"Review organic performance first; paid boost requires explicit approval.","landing_page_need":"Review whether an AMTL page or offer exists before any paid action.","budget_state":"approval_required","external_publish_performed":false,"paid_action_performed":false,"human_review_required":true},"ripple_packet":{"plan_id":"social-calendar-amtl-linkedin-data-care-series-posts-1-12-v0-3-final-0e08aea6","content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","platform":"LinkedIn","expected_lead_type":"Business owner, founder, operator, or technology decision-maker interested in practical AI adoption.","cta":"Ask what workflow, risk, or decision they want AI to make easier.","likely_questions":["How would this apply to my business?","What can be automated safely?","How do I prove AI output is reliable?"],"follow_up_angle":"Offer a practical review conversation, not a hard sell.","buying_intent_posts":[{"item_id":"li-data-care-01","day_index":1,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-20","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 1","working_angle":"","content_format":"linkedin_image_post","body_text":"Every business has one spreadsheet that runs everything.\n\nNobody remembers who built it. Three people have their own copy. The newest version is called FINAL_v7_REAL.xlsx, probably.\n\nHere is the part we find interesting: nobody ever decided that file would become load-bearing. It just did, one quiet week at a time.\n\nThe risk is not the spreadsheet. Spreadsheets are wonderful tools. The risk is the silence around it: no owner, no backup plan, no one who can say what breaks if it is wrong.\n\nField audits of operational spreadsheets keep finding the same thing: most of the ones auditors open contain at least one error.\n\nWhich spreadsheet would hurt most if it was wrong this week?","sources":[{"label":"audit claim source","url":"https://panko.com/ssr/Audits.html"}],"assets":[{"filename":"li-card-01.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Source for the audit claim: https://panko.com/ssr/Audits.html Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"draft_needs_human_review","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-02","day_index":2,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-24","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 2","working_angle":"","content_format":"linkedin_image_post","body_text":"A customer rings to question a quote.\n\nSales opens the CRM: one address. Accounts opens the invoicing tool: another. Marketing's list has a third, plus a first name spelled two ways.\n\nNobody in this story made a mistake. The business simply never picked which system wins when they disagree.\n\nSo the answer to \"which one is right?\" becomes whoever checked last. That is not a data strategy. That is a coin flip with a polite voice.\n\nThe fix is not a big migration project. It starts smaller: know where the same record lives twice, and decide, once, who owns the winner.\n\nHow many systems in your business think they own the customer record?","sources":[],"assets":[{"filename":"li-card-02.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"draft_needs_human_review","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-03","day_index":3,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-26","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 3","working_angle":"","content_format":"linkedin_image_post","body_text":"Every owner we meet locks the office at night and knows exactly where the keys are.\n\nAsk the same owner where the customer details sit, and the honest answer is usually a wave: \"in the system somewhere.\"\n\nSomewhere is inboxes. Somewhere is an export on a laptop from March. Somewhere is the shared drive folder called Old Stuff.\n\nThis is not carelessness. It is what happens when data grows faster than anyone's map of it.\n\nThe first step in protecting sensitive information is unglamorous: knowing where it is. A map before a lock.\n\nIf a customer asked tonight where their details are stored, how long would an honest answer take?","sources":[],"assets":[{"filename":"li-card-03.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Australia's breach statistics, for context: https://www.oaic.gov.au/privacy/notifiable-data-breaches/notifiable-data-breach-statistics-dashboard Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"draft_needs_human_review","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-04","day_index":4,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-11-30","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 4","working_angle":"","content_format":"linkedin_image_post","body_text":"Picture the most common data breach in Australia.\n\nIt is not a hooded figure in a dark room. It is a normal Tuesday. Someone is flat out, autocomplete grabs the wrong name, and a spreadsheet of customer details goes to a stranger.\n\nFrom that moment a clock starts. Australian privacy law gives a business up to 30 days to assess whether the mistake is serious enough to report, and the OAIC expects you to show your working.\n\nThink about what that assessment needs: what was in the file, whose details, where else the file lived, who else got it.\n\nMost businesses would be answering those questions for the first time, during the worst week of their year.\n\nThe businesses that cope are the ones that already had the answers written down.","sources":[],"assets":[{"filename":"li-card-04.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment at publish: Current breach statistics and trends: https://www.oaic.gov.au/news/media-centre/data-breach-notifications-increase-to-all-time-high-in-2025,-new-ndb-stats-show Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"draft_needs_human_review","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"li-data-care-05","day_index":5,"content_pack":"AMTL LinkedIn data care series posts 1-12 (v0.3 FINAL)","domain":"data care","platform":"LinkedIn","account":"amtl_page","scheduled_date":"2026-12-02","scheduled_time":"08:00","timezone":"Australia/Sydney","slot":"weekday-2day-cadence","slot_type":"post","theme":"data care awareness","topic":"AMTL LinkedIn data care series post 5","working_angle":"","content_format":"linkedin_image_post","body_text":"Nine words: \"Show me everything you hold about me.\"\n\nA customer can ask that, in Australia, today, by email, for free. And behind that one sentence is a treasure hunt: the CRM, the invoicing tool, the support inbox, the marketing list, the spreadsheets, the backups.\n\nFor a well-run business it is an afternoon. For most it is a fortnight of archaeology, and the honest answer is still \"we think that is everything.\"\n\nWe keep coming back to the same thought: the question is simple, so the answer should be simple too. It only gets hard when the records were never kept with that question in mind.\n\nIf that email arrived tomorrow morning, who in your business would own the reply?","sources":[],"assets":[{"filename":"li-card-05.png","kind":"quote_card","clearance":"approved","source":"li-cards-1-12-c64cd3f6.zip sha256 47dce94ded1374be23b0f99d29a208d176161e008b2b181eeb4ce845099bd313"}],"notes":"First comment: none planned (no external claim to source). Quote on card is on the image only.","asset_needed":"Approved visual attached to the content pack","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"AMTL-LinkedIn-data-care-final-posts-1-12-v0.3-191126.docx (Drive 1Uqt2seNOzdvDXYBNzwO2ODb4Drau-5Gm)","evidence_link":"/api/source-vault","approval_state":"draft_needs_human_review","approval_evidence_message_id":"","source_message_ids":["wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNTNEMkFBOTI4NzQzMTcyNTg2AA=="],"flags":["approval not covered by the operator-supplied registry - demoted"],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"crm_customer_write_performed":false,"external_send_performed":false,"human_review_required":true}},{"id":7,"plan_id":"social-calendar-30-days-of-linkedin-ai-posts-58acbfab","pack_name":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","start_date":"2026-11-20","posting_time":"09:10","timezone":"Australia/Sydney","item_count":1,"artifact_dir":"/var/lib/bada/exports/bada-bing-social-calendar-social-calendar-30-days-of-linkedin-ai-posts-58acbfab","external_publish_performed":false,"target_app_write_performed":false,"human_review_required":true,"created_at":"2026-11-18T18:39:44.997557+00:00","receipt_hash":"756da64441373b6c5e289f9d16df66155bde9c91208cf89320ce58fedf528814","customer_id":"amtl","archived":false,"archive_note":"","source_artifact":"","schedule":[{"item_id":"preview-item-191126-1","day_index":1,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","account":"personal","scheduled_date":"2026-11-20","scheduled_time":"09:10","timezone":"Australia/Sydney","slot":"morning","slot_type":"post","theme":"AI answer visibility","topic":"AI search visibility for small brands","working_angle":"Founder-led practical take","content_format":"linkedin_text_post","body_text":"Draft placeholder for day 1: how small brands show up in AI answers. Text to be replaced by the model-generated draft once the local model is online.","sources":[],"assets":[],"notes":"Imported by recovery task agent as preview draft; approval_state stays draft_needs_human_review.","asset_needed":"No visual required","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"Owner-approved content pack JSON.","evidence_link":"/api/source-vault","approval_state":"draft_needs_human_review","approval_evidence_message_id":"","source_message_ids":[],"flags":[],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"filtered_item_count":1,"spark_packet":{"plan_id":"social-calendar-30-days-of-linkedin-ai-posts-58acbfab","content_pack":"30 Days of LinkedIn AI Posts","platform":"LinkedIn","date_range":{"start":"2026-11-20","end":"2026-11-20"},"domain_mix":["AI"],"post_count":1,"boost_candidates":[],"cta":"Review organic performance first; paid boost requires explicit approval.","landing_page_need":"Review whether an AMTL page or offer exists before any paid action.","budget_state":"approval_required","external_publish_performed":false,"paid_action_performed":false,"human_review_required":true},"ripple_packet":{"plan_id":"social-calendar-30-days-of-linkedin-ai-posts-58acbfab","content_pack":"30 Days of LinkedIn AI Posts","platform":"LinkedIn","expected_lead_type":"Business owner, founder, operator, or technology decision-maker interested in practical AI adoption.","cta":"Ask what workflow, risk, or decision they want AI to make easier.","likely_questions":["How would this apply to my business?","What can be automated safely?","How do I prove AI output is reliable?"],"follow_up_angle":"Offer a practical review conversation, not a hard sell.","buying_intent_posts":[{"item_id":"preview-item-191126-1","day_index":1,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","account":"personal","scheduled_date":"2026-11-20","scheduled_time":"09:10","timezone":"Australia/Sydney","slot":"morning","slot_type":"post","theme":"AI answer visibility","topic":"AI search visibility for small brands","working_angle":"Founder-led practical take","content_format":"linkedin_text_post","body_text":"Draft placeholder for day 1: how small brands show up in AI answers. Text to be replaced by the model-generated draft once the local model is online.","sources":[],"assets":[],"notes":"Imported by recovery task agent as preview draft; approval_state stays draft_needs_human_review.","asset_needed":"No visual required","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"Owner-approved content pack JSON.","evidence_link":"/api/source-vault","approval_state":"draft_needs_human_review","approval_evidence_message_id":"","source_message_ids":[],"flags":[],"status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"crm_customer_write_performed":false,"external_send_performed":false,"human_review_required":true}},{"id":6,"plan_id":"social-calendar-30-days-of-linkedin-ai-posts-5e0839d9","pack_name":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","start_date":"2026-11-18","posting_time":"09:10","timezone":"Australia/Sydney","item_count":30,"artifact_dir":"/var/lib/bada/exports/bada-bing-social-calendar-social-calendar-30-days-of-linkedin-ai-posts-5e0839d9","external_publish_performed":false,"target_app_write_performed":false,"human_review_required":true,"created_at":"2026-11-18T18:26:57.207600+00:00","receipt_hash":"c9acef1b6e211c6d6c68a461de18bd320e4e438e0d622d615b08da6147487ec7","customer_id":"amtl","archived":false,"archive_note":"","source_artifact":"","schedule":[{"item_id":"calendar-item-01","day_index":1,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-18","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-02","day_index":2,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-19","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-03","day_index":3,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-20","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-04","day_index":4,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-23","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"measuring AI answers about your brand","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-05","day_index":5,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-24","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"practical prompt workflows","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-06","day_index":6,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-25","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-07","day_index":7,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-26","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-08","day_index":8,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-27","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-09","day_index":9,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-30","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"measuring AI answers about your brand","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-10","day_index":10,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-01","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"practical prompt workflows","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-11","day_index":11,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-02","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-12","day_index":12,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-03","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-13","day_index":13,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-04","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-14","day_index":14,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-07","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"measuring AI answers about your brand","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-15","day_index":15,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-08","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"practical prompt workflows","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-16","day_index":16,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-09","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-17","day_index":17,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-10","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-18","day_index":18,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-11","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-19","day_index":19,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-14","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"measuring AI answers about your brand","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-20","day_index":20,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-15","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"practical prompt workflows","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-21","day_index":21,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-16","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-22","day_index":22,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-17","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-23","day_index":23,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-18","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-24","day_index":24,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-21","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"measuring AI answers about your brand","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-25","day_index":25,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-22","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"practical prompt workflows","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-26","day_index":26,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-23","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-27","day_index":27,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-24","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-28","day_index":28,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-25","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-29","day_index":29,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-28","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"measuring AI answers about your brand","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-30","day_index":30,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-12-29","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"practical prompt workflows","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"filtered_item_count":30,"spark_packet":{"plan_id":"social-calendar-30-days-of-linkedin-ai-posts-5e0839d9","content_pack":"30 Days of LinkedIn AI Posts","platform":"LinkedIn","date_range":{"start":"2026-11-18","end":"2026-12-29"},"domain_mix":["AI"],"post_count":30,"boost_candidates":[{"item_id":"calendar-item-01","day_index":1,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-18","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-02","day_index":2,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-19","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-03","day_index":3,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-20","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"cta":"Review organic performance first; paid boost requires explicit approval.","landing_page_need":"Review whether an AMTL page or offer exists before any paid action.","budget_state":"approval_required","external_publish_performed":false,"paid_action_performed":false,"human_review_required":true},"ripple_packet":{"plan_id":"social-calendar-30-days-of-linkedin-ai-posts-5e0839d9","content_pack":"30 Days of LinkedIn AI Posts","platform":"LinkedIn","expected_lead_type":"Business owner, founder, operator, or technology decision-maker interested in practical AI adoption.","cta":"Ask what workflow, risk, or decision they want AI to make easier.","likely_questions":["How would this apply to my business?","What can be automated safely?","How do I prove AI output is reliable?"],"follow_up_angle":"Offer a practical review conversation, not a hard sell.","buying_intent_posts":[{"item_id":"calendar-item-01","day_index":1,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-18","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"AI search visibility for small brands","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-02","day_index":2,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-19","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"answer engine optimization basics","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-03","day_index":3,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-20","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"founder-led content systems","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-04","day_index":4,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-23","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"measuring AI answers about your brand","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true},{"item_id":"calendar-item-05","day_index":5,"content_pack":"30 Days of LinkedIn AI Posts","domain":"AI","platform":"LinkedIn","scheduled_date":"2026-11-24","scheduled_time":"09:10","timezone":"Australia/Sydney","topic":"practical prompt workflows","content_format":"LinkedIn text post","asset_needed":"Optional proof card or simple branded visual","cta":"Invite a thoughtful reply or ask for a practical use case.","source_artifact":"User-provided 30-day content pack or current Bada source context.","evidence_link":"/api/source-vault/3","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"low","spark_sync_state":"not_created","ripple_sync_state":"not_created","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"human_review_required":true}],"crm_customer_write_performed":false,"external_send_performed":false,"human_review_required":true}},{"id":5,"plan_id":"social-calendar-import-linkedin-weeks-three-and-four-owner-appr-f5ac8b46e499f966ff8c7deab072c58322d08c8716d27b5a8b452b40875a9527","pack_name":"LinkedIn weeks three and four - owner approved31to60","domain":"mixed","platform":"linkedin","start_date":"2026-11-30","posting_time":"per-item","timezone":"Australia/Sydney","item_count":30,"artifact_dir":"","external_publish_performed":false,"target_app_write_performed":false,"human_review_required":true,"created_at":"2026-11-14T18:19:49.213776+00:00","receipt_hash":"971bbe8169bb6cf89f1a0c67e2908f0297dcfdfc0eb0a5f3ed25f70fca97b7e2","customer_id":"amtl","archived":false,"archive_note":"","source_artifact":"LinkedIn weeks three and four.docx","schedule":[{"item_id":"li-2026-11-30-personal-daytime","day_index":1,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"AI","platform":"linkedin","scheduled_date":"2026-11-30","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The model is open. Can the whole system be replaced?","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"AI","working_angle":"The model is open. Can the whole system be replaced?","angle_is_final_headline":false,"body_text":"The model is open. The exit may still be narrow.\n\nImagine a team moving an AI service to a different model. The weights are available. The application still depends on a particular search index, a private scoring service, a prompt format and a collection of tests nobody can export.\n\nThe part advertised as open is replaceable. The service the customer relies on is another question.\n\nThere is no need to dismiss open models to notice this. Openness can be valuable without solving every dependency around it. The mistake is asking one label to answer a whole operating question.\n\nTry a small replacement rehearsal. Choose one ordinary task and a second model. Keep the expected result fixed. Note what has to change, what cannot move and which checks stop being useful.\n\nA poor result could expose a model limitation. It could also expose an undocumented assumption in the surrounding system. Those require different repairs.\n\nThe most useful exit plan may begin with something smaller than migration: a test set owned by the team, a documented interface, an export that another system can actually read.\n\nThere will be cases where the cost of that independence exceeds its present value. That is a choice worth making openly. It is different from discovering the cost when the supplier changes terms.\n\nAsk what can be replaced, by whom, and with how much work. Then decide which dependencies to accept.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-30-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"Test the exit, not the label: model, interface, search and evaluation. Which parts can move?","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.440464+00:00"},{"item_id":"li-2026-11-30-amtl_page-page","day_index":2,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Cyber","platform":"linkedin","scheduled_date":"2026-11-30","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"A useful log should not become a second data breach.","content_format":"LinkedIn long-form article","account":"amtl_page","slot":"daytime","slot_type":"business_article","theme":"Cyber","working_angle":"A useful log should not become a second data breach.","angle_is_final_headline":false,"body_text":"A log helps explain what happened. It can also preserve something that should never have been copied.\n\nImagine an application recording every failed request in full. Troubleshooting becomes easier. The same record now contains a customer's private message, an access token and a document the support team did not need to see.\n\nCalling that record diagnostic data does not change what is in it.\n\nDecide what question the log must answer\n\nStart with an event, not a dump. For a failed approval, the useful question may be whether a request arrived, which rule rejected it and whether any external action occurred. That does not automatically require the request's full contents.\n\nA deliberately chosen event identifier can help connect stages without repeating the sensitive payload. The identifier still needs protection where it can be linked back to a person or account.\n\nThe question shapes the fields. It should also shape who can search them and how long they are retained.\n\nKeep the record below the sensitivity of the event where possible\n\nOWASP's Logging Cheat Sheet advises against recording access tokens, passwords and sensitive personal information directly. Its guidance discusses removing, masking, sanitising, hashing or encrypting different kinds of data, with treatment chosen for the risk.\n\nThese techniques are not interchangeable. A reversible encryption scheme and a one-way transformation solve different problems. Removing a field entirely may be safer than retaining a transformed copy that serves no real diagnostic purpose.\n\nNor does a filter make unrestricted logging safe. Filters can miss a new field, an unexpected exception message or a copied document embedded in another value.\n\nTest the failure path\n\nUse synthetic sensitive markers in a safe test environment. Trigger the errors the team actually investigates: failed authentication, rejected uploads, upstream timeouts and permission changes. Look at what reaches each destination, including monitoring services and exported support files.\n\nCheck the access path as well. A carefully limited application log offers little comfort if its bulk export is available to a much wider group.\n\nGive retention a reason\n\nA record can be useful today and unnecessary later. Agree what each event type supports, who owns the retention decision and how deletion is checked. A longer retention period should have a reason beyond the possibility that someone might ask one day.\n\nThis is an engineering review pattern, not a legal retention schedule. Sector, contract and jurisdiction can change the requirements.\n\nThe aim is enough evidence to investigate the event, with less private material to protect afterwards. More detail is not automatically more accountability.\nhttps://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-30-amtl_page-page-owner.png","caption":"Visual created with ChatGPT","alt_text":"Enough evidence, less private data: event, rule and outcome beside a lock. Keep only what the incident needs.","clearance":"pending"}],"sources":[{"title":"Logging Cheat Sheet","url":"https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html","publisher":"OWASP","accessed_date":"2026-11-14","note":"Data-to-exclude and log-protection guidance. Review pattern is original, not a compliance guarantee."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.449819+00:00"},{"item_id":"li-2026-11-30-personal-evening","day_index":3,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Culture / language","platform":"linkedin","scheduled_date":"2026-11-30","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"The same word asks two people to do different jobs.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Culture / language","working_angle":"The same word asks two people to do different jobs.","angle_is_final_headline":false,"body_text":"\"Soon\" can end one person's worry and begin another person's waiting.\n\nFor the speaker it may mean, \"I have not forgotten.\" For the listener it may mean, \"I can plan around this happening today.\"\n\nNeither person needs to be careless for the gap to cause trouble. They have attached different obligations to the same small word.\n\nOther words do similar work: simple, urgent, finished, support. They sound shared before their consequences are shared.\n\nWe could respond by trying to define every word before speaking. That would make ordinary conversation unbearable. A more useful habit is to notice when a word starts carrying a decision.\n\nIf someone is about to promise a customer a date, ask what \"soon\" means here. If someone is about to close a job, ask what remains under \"finished\".\n\nThe question need not be an accusation. \"So I can plan, which day should I use?\" is different from \"Why are you being vague?\"\n\nClarity is sometimes mistaken for coldness. It can be a form of consideration: one person takes a little more care with the sentence so another person does not have to carry the uncertainty.\n\nLeave room for ordinary language. Become precise where somebody has to act on it.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-30-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Soon: a reassurance or a planning date? Define the word when someone must act.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.460240+00:00"},{"item_id":"li-2026-12-01-personal-daytime","day_index":4,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Cyber","platform":"linkedin","scheduled_date":"2026-12-01","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Two safeguards can share one weak point.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Cyber","working_angle":"Two safeguards can share one weak point.","angle_is_final_headline":false,"body_text":"The second safeguard looks reassuring until we ask what the first one depends on.\n\nImagine a service with a primary administrator and an emergency administrator. Different accounts. Different passwords. Both recovery links go to the same mailbox.\n\nThat mailbox is no longer just another account. It is a shared dependency beneath the two controls.\n\nThis does not make every shared dependency unacceptable. It makes it visible. Two controls can protect against one kind of failure while remaining exposed to another.\n\nNIST's zero trust guidance separates authentication from authorisation and focuses protection on resources rather than assuming that location or ownership establishes trust. A useful extension in a practical review is to draw how access can be recovered, not only how it is normally granted.\n\nWhich mailbox resets the account? Which administrator can change that mailbox? Where is the emergency access record held? Who can reach it if the normal sign-in system fails?\n\nDo not test this by breaking the only working recovery path. Map it first, then rehearse safely with the people responsible for the service.\n\nThe drawing may reveal a deliberate trade-off. A small business may accept some concentration of control. At least it can then protect that point with the attention it deserves.\n\nCounting safeguards is easier than checking their independence. The second task tells us more about what can fail together.\nhttps://csrc.nist.gov/pubs/sp/800/207/final","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/shared-recovery.png","caption":"Original conceptual diagram, composed from text and vector shapes; illustrative, not measured data. No generative-image service used.","alt_text":"Two separate administrator accounts feed one shared recovery mailbox.","ai_origin_labelled":false,"clearance":"not_required"}],"sources":[{"title":"Zero Trust Architecture, SP 800-207","url":"https://csrc.nist.gov/pubs/sp/800/207/final","publisher":"NIST","accessed_date":"2026-11-14","note":"Abstract separates authentication and authorisation and focuses on resources. Recovery/offboarding examples and maps are original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"not_required_asserted","image_clearance_assertions":["not_required"],"scheduling_blocked":"","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-12-01-personal-evening","day_index":5,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Reserve: process judgement","platform":"linkedin","scheduled_date":"2026-12-01","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"Before adding a step, name the mistake it will prevent.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"reserve","theme":"Reserve: process judgement","working_angle":"Before adding a step, name the mistake it will prevent.","angle_is_final_headline":false,"body_text":"The new form has a field for everything. The old mistake still gets through.\n\nImagine a team adding a mandatory comment after a missed check. People learn to type \"checked\". The system records completion. Nobody is any clearer about what was examined.\n\nThe team has added evidence of typing, not evidence of judgement.\n\nBefore adding a step, name the mistake it is meant to prevent. Then ask what information would let someone detect that mistake while there is still time to act.\n\nSometimes a required field is exactly right. A missing delivery address is not a philosophical problem. At other times the useful change is a worked example, a second pair of eyes or a choice that cannot be made until the relevant evidence appears.\n\nIt helps to separate two questions. Do we need to stop an action? Or do we need to understand later why someone took it? A control designed for one job can become needless friction when used for the other.\n\nIf the extra step adds work, be willing to remove an old one that no longer serves a purpose. Otherwise every past mistake becomes a permanent tax on the next person.\n\nA process can remember what went wrong without asking everyone to repeat the paperwork forever.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-01-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"What mistake should this step prevent? Stop an action or support a later review. Choose the control for the job.","clearance":"pending"}],"sources":[],"reserve_fallback":true,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.468536+00:00"},{"item_id":"li-2026-12-02-personal-daytime","day_index":6,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Business","platform":"linkedin","scheduled_date":"2026-12-02","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"We priced the hour. The customer bought a result.","content_format":"LinkedIn long-form article","account":"personal","slot":"daytime","slot_type":"business_article","theme":"Business","working_angle":"We priced the hour. The customer bought a result.","angle_is_final_headline":false,"body_text":"The quote says forty hours. The customer thinks they are buying a working answer.\n\nBoth descriptions can be honest. They can still leave a dangerous gap.\n\nImagine a small consultancy asked to improve an ordering process. Its estimate covers workshops, analysis and a report. The buyer expects fewer failed orders. A report arrives on time. The buyer asks when the improvement will begin.\n\nThe disagreement did not start with the invoice. It started when effort and outcome were allowed to sound like the same promise.\n\nMake the thing being bought visible\n\nAn hourly price describes a charging method. It does not, by itself, describe completion. A fixed fee has the same limitation: it fixes a number without necessarily fixing a shared understanding.\n\nBefore choosing a pricing model, describe the deliverable and the decision it supports. Is the team buying a diagnosis, an implemented change, a tested release or an ongoing service? Each ends in a different place.\n\nThen identify what the supplier controls. A consultant may control the quality of the analysis while depending on the client for access, staffing and decisions. Pretending those dependencies do not exist does not make a stronger promise. It makes an argument more likely.\n\nSeparate completion from improvement\n\nA sensible agreement can name both. Completion might mean that a proposed workflow has been tested against agreed scenarios and handed over to named owners. Improvement might mean a change in error rate over a later period, with a defined baseline and enough context to interpret it.\n\nThose are examples, not standard contract terms. The point is to stop one measure quietly replacing the other.\n\nIf the supplier guarantees an outcome, the price must reflect what it is taking responsibility for. If it does not, the buyer should not have to discover that distinction after delivery.\n\nTreat change as a conversation about the promise\n\nA new requirement is not simply another task. It can alter the evidence needed for completion, the dependencies or the result someone expects.\n\nA useful change discussion asks what is now different, what remains included and who accepts the effect on cost or time. It does not hide behind the fact that the original number of hours has been used.\n\nKeep the customer's problem in view\n\nThe UK Government Service Standard asks teams to solve a whole problem for users, rather than treating one transaction in isolation. Commercial work has a related tension: a supplier can fulfil a narrow scope while the customer's problem remains unsolved.\n\nThat does not mean every supplier should accept an unlimited problem. It means the boundary should be explained in language the buyer can recognise.\n\nA carefully bounded service can be valuable. So can paid discovery that concludes the proposed project should not proceed. Neither needs to borrow the appearance of a guaranteed business result.\n\nThe best pricing conversation may start before the price: when this work is finished, what will each of us be able to say is different?\nhttps://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-02-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"What is the customer buying? Effort, deliverable or business result. Different promises need different evidence.","clearance":"pending"}],"sources":[{"title":"Solve a whole problem for users","url":"https://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem","publisher":"Government Digital Service","accessed_date":"2026-11-14","note":"Whole-problem design principle only. Pricing and contract example is hypothetical, not legal advice."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.478187+00:00"},{"item_id":"li-2026-12-02-amtl_page-page","day_index":7,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Process","platform":"linkedin","scheduled_date":"2026-12-02","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The task took twelve minutes. The request took four days.","content_format":"LinkedIn image post","account":"amtl_page","slot":"daytime","slot_type":"post","theme":"Process","working_angle":"The task took twelve minutes. The request took four days.","angle_is_final_headline":false,"body_text":"The task took twelve minutes. The request took four days.\n\nImagine a case that waited in an inbox, moved to a specialist, returned for one missing detail, then waited again. Making the twelve-minute task twice as fast would help the person doing it. It would barely change the customer's wait.\n\nThese are illustrative numbers, not a benchmark. Their purpose is to separate two clocks.\n\nWorking time measures time spent doing the task. Elapsed time includes what happened between arrival and completion. Both can be useful, but they answer different questions.\n\nFollow a few real requests from start to finish. Record when each became ready, when work began, when it stopped and why. Include time spent waiting for the customer, while checking whether the request for information was clear in the first place.\n\nDo not turn this into a contest to keep everyone continuously busy. A specialist with no spare capacity may leave urgent requests waiting longer. Nor should a necessary review be removed merely because it takes time.\n\nAsk which waits protect the outcome, which reflect a capacity choice and which exist because nobody can see the next handover.\n\nOnly then choose the improvement. Sometimes it is faster work. Sometimes it is a clearer input, a smaller batch or a named person allowed to move the case forward.\n\nA stopwatch at the workbench cannot explain the whole queue.","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/two-clocks.png","caption":"Original conceptual diagram, composed from text and vector shapes; illustrative, not measured data. No generative-image service used.","alt_text":"Working time and elapsed time answer different questions; illustrative wait-work sequence is not time-scaled.","ai_origin_labelled":false,"clearance":"not_required"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"not_required_asserted","image_clearance_assertions":["not_required"],"scheduling_blocked":"","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-12-02-personal-evening","day_index":8,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Learning / everyday life","platform":"linkedin","scheduled_date":"2026-12-02","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"The apology explains everything except the harm.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Learning / everyday life","working_angle":"The apology explains everything except the harm.","angle_is_final_headline":false,"body_text":"An explanation can be accurate and still arrive too early.\n\nImagine someone saying, \"I missed the deadline because the system failed, the handover was unclear and I had another urgent job.\"\n\nAll of that may be true. The person waiting still needs to know whether their loss has been understood.\n\nAn apology does a different job from a cause analysis. One recognises the effect on another person and takes responsibility for the part that is ours. The other helps explain how it happened and what might prevent it happening again.\n\nWe need not choose between them. We do need to notice when the explanation is crowding out the acknowledgement.\n\n\"You had to change your plans because I did not tell you in time\" names something more specific than \"sorry for any inconvenience\". It also leaves less room to pretend that the only problem was how the message was received.\n\nA repair may be possible. It may also be incomplete, unwelcome or too late. Offering it does not purchase forgiveness, and an apology is not a demand that the other person end the conversation.\n\nPerhaps the useful pause is this: before explaining what made my action understandable, can I show that I understand what it did?\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-02-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Before the explanation: name the effect, own your part, offer a repair. Leave room for the answer.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.487295+00:00"},{"item_id":"li-2026-12-03-personal-daytime","day_index":9,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Business","platform":"linkedin","scheduled_date":"2026-12-03","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"We retired the product. Its promises kept running.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Business","working_angle":"We retired the product. Its promises kept running.","angle_is_final_headline":false,"body_text":"The product has an end date. The promises around it may not.\n\nImagine a service being retired. New sales stop on Friday. Existing customers still have records to retrieve, integrations to replace and questions about what happens to work already submitted.\n\nInternally, the product may belong to the past. For those customers, it remains a live dependency.\n\nA retirement plan needs more than a final notice. It needs a map of the obligations that outlive the last sale: access, support, exports, deletion, billing and the handling of unresolved work.\n\nSome will be contractual or legal obligations that need qualified review. Others are choices about how to treat people who relied on the service. It is worth keeping those categories clear rather than calling every considerate action mandatory or every unlisted need optional.\n\nTry reading the plan from the customer's side. What must they do? What can they postpone? What will become impossible after each date? Who can help if the standard route does not work?\n\nA long notice period can still be unhelpful if it contains no usable next step. A short message can be valuable if it explains exactly what changes and how to prepare.\n\nStopping development is an internal decision. Ending a dependency is shared work. A responsible exit gives the people on the other side enough clarity to begin theirs.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-03-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"The last sale is not the last obligation. Access, support, export, deletion and unresolved work extend beyond the sale.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.497124+00:00"},{"item_id":"li-2026-12-03-personal-evening","day_index":10,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Inclusion","platform":"linkedin","scheduled_date":"2026-12-03","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"Before we praise resilience, check the barrier.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"special","theme":"Inclusion","working_angle":"Before we praise resilience, check the barrier.","angle_is_final_headline":false,"body_text":"Before we praise someone's resilience, it is worth asking what they had to work around.\n\nA form that cannot be used with a keyboard. A meeting whose documents arrive too late to be converted into an accessible format. A support process that permits only one way to communicate.\n\nThese are design decisions, not tests of character.\n\nOn the International Day of Persons with Disabilities, a useful question for a team is not how inspiring its language sounds. It is whose participation depends on repeated personal negotiation.\n\nPeople with disabilities are not one group with one preferred solution. Ask those affected, include them in decisions and make room for different needs. Do not turn one person's successful workaround into proof that the barrier is acceptable.\n\nSome changes require substantial work. Others begin with a less dramatic habit: accessible source documents, clear instructions, more than one contact route, and time to ask what an individual needs without making them explain it to every new person.\n\nW3 C's guidance on labels and instructions gives one practical example. A field should tell a person what input it expects. Making someone discover that through repeated errors is avoidable work.\n\nRecognition is welcome. Removing a barrier is a different contribution, and it should not depend on someone first being exceptional at overcoming it.\nhttps://www.un.org/en/observances/day-of-persons-with-disabilities\nhttps://www.w3.org/WAI/WCAG22/Understanding/labels-or-instructions\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-03-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Participation should not require a workaround: find the barrier, ask those affected and change the design.","clearance":"pending"}],"sources":[{"title":"International Day of Persons with Disabilities","url":"https://www.un.org/en/observances/day-of-persons-with-disabilities","publisher":"United Nations","accessed_date":"2026-11-14","note":"Annual3 December observance. Page still shows2025 theme; no2026 theme claimed. Inclusion reflection is original."},{"title":"Understanding SC 3.3.2: Labels or Instructions","url":"https://www.w3.org/WAI/WCAG22/Understanding/labels-or-instructions","publisher":"W3 C WAI","accessed_date":"2026-11-14","note":"User-input labels or instructions. No general accessibility-conformance claim is made."}],"reserve_fallback":false,"special_day":"International Day of Persons with Disabilities","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.506608+00:00"},{"item_id":"li-2026-12-04-personal-daytime","day_index":11,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Philosophy / learning","platform":"linkedin","scheduled_date":"2026-12-04","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"What changes when a teacher can be questioned?","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Philosophy / learning","working_angle":"What changes when a teacher can be questioned?","angle_is_final_headline":false,"body_text":"A good explanation can survive a sincere question.\n\nThat does not mean a teacher must have an immediate answer to everything. It means the question is not treated as an offence against the teacher.\n\nThere is a difference between questioning an idea and trying to win a room. There is also a difference between respecting knowledge and agreeing that it cannot be examined.\n\nA learner can do some work before asking: listen carefully, try the reasoning, identify the point that does not follow. A teacher can distinguish that effort from a challenge to their status.\n\nThe most useful reply may be, \"That is outside what I know,\" or \"Here is why I think this, and here is where the argument is weaker.\"\n\nThose replies do not erase authority. They show what it is made of. The learner gets a way to assess a claim rather than an instruction to borrow someone else's certainty.\n\nThis applies beyond a classroom. In a workplace, an expert can answer the immediate question while quietly teaching everyone else which questions are safe to ask next time.\n\nWe should be wary of the room in which agreement is mistaken for understanding. A question can slow the explanation and improve the learning.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-04-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"A question can improve the learning: claim, reason, check and question form a cycle.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.515054+00:00"},{"item_id":"li-2026-12-04-amtl_page-page","day_index":12,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Automation","platform":"linkedin","scheduled_date":"2026-12-04","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Undo is easy to promise before a workflow leaves the screen.","content_format":"LinkedIn long-form article","account":"amtl_page","slot":"daytime","slot_type":"business_article","theme":"Automation","working_angle":"Undo is easy to promise before a workflow leaves the screen.","angle_is_final_headline":false,"body_text":"The interface has an undo button. The supplier has already dispatched the parcel.\n\nThat fictional example points to a common automation design problem: reversing an internal record is not the same as reversing the outside world.\n\nA workflow may update a database, send a message, reserve stock and request a payment. Those actions do not share one universal undo operation.\n\nDraw the effects separately\n\nBefore automating a sequence, list what each step changes and where. Some changes remain inside a system that supports a transaction. Others create a request to another service. Others reach a person who may act immediately.\n\nFor each, ask how the team will know whether the action happened. Then ask whether it can be cancelled, corrected or only followed by a new action.\n\nA refund is not an erased charge. A correction email does not make the first message unread. Returning stock does not remove the time a customer spent resolving the problem.\n\nThese distinctions help set a truthful expectation of recovery.\n\nPlan a compensating action before relying on it\n\nIn a hypothetical ordering workflow, reserving stock might be followed by a failed payment. The business may choose to release the reservation. That is a new action with its own failure path and ownership.\n\nThe release might be delayed. Someone may have changed the order in the meantime. A second workflow may already be using the reservation. Treating compensation as another blind command risks creating a second inconsistency.\n\nThe recovery design should identify the current state, permitted next action and the person who owns a case that cannot be repaired automatically. It also needs a way to prevent the same case being independently repaired twice.\n\nDescribe partial completion honestly\n\nA customer should not be told that everything failed if one external action succeeded. Nor should a green internal status hide a failed downstream action.\n\nChoose statuses that correspond to an operational decision: awaiting confirmation, partly completed, recovery in progress, needs a person. These are example labels, not a prescribed standard. Their value is whether someone knows what to do next.\n\nTest recovery with realistic interruptions\n\nIn a safe environment, interrupt the workflow after each consequential step. Check which actions occurred, which records explain them and whether the proposed recovery is still valid.\n\nInclude the awkward case where an outside service answers late. A repair based on an assumed failure can collide with an action that was merely delayed.\n\nThe objective is not a promise that every action can be undone. It is a plan that acknowledges which consequences persist, and gives someone responsibility for them.\n\nAutomation becomes easier to trust when its recovery story is as specific as its success story.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-04-amtl_page-page-owner.png","caption":"Visual created with ChatGPT","alt_text":"Undo is not one operation: cancel, correct or compensate. Some consequences remain.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.523792+00:00"},{"item_id":"li-2026-12-04-personal-evening","day_index":13,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Literature / quote note","platform":"linkedin","scheduled_date":"2026-12-04","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"A letter reaches the listener who was in the room.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Literature / quote note","working_angle":"A letter reaches the listener who was in the room.","angle_is_final_headline":false,"body_text":"\"I am half agony, half hope.\"\n\nIn Jane Austen's Persuasion, Captain Wentworth writes those words to Anne Elliot while listening to a conversation nearby. His letter responds to what he has heard her say about constancy.\n\nThe same words might feel theatrical if they arrived without that scene. Within it, the letter is a risk taken by someone who cannot be certain what the answer will be.\n\nThat is one reason a quotation can lose something when we detach it from its listener. We preserve the sentence and remove the uncertainty that gave it weight.\n\nAusten lets us see the distance between what people feel, what they can say in company and what another person is able to hear. Meaning moves through those constraints. It is not sitting intact inside a beautiful line, waiting to be extracted.\n\nThere is a lesson here for reading, without turning the novel into a manual for communication. Before deciding what a sentence proves, ask who is speaking, to whom, and at what point in the story.\n\nA line can be true to a character's moment without being advice for everybody.\n\nSometimes going back to the page gives us something better than a quotation to keep: a person to understand.\nhttps://janeaustens.house/learn/school-visits/online-resources/captain-wentworths-letter/\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-04-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Who is speaking, to whom, and is AI part of the story? Context changes what a line can carry.","clearance":"pending"}],"sources":[{"title":"Captain Wentworth's letter","url":"https://janeaustens.house/learn/school-visits/online-resources/captain-wentworths-letter/","publisher":"Jane Austen's House","accessed_date":"2026-11-14","note":"Persuasion chapter 23, direct short quotation and scene context. Interpretation is original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.534102+00:00"},{"item_id":"li-2026-12-05-personal-one_piece","day_index":14,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Reflection / volunteering","platform":"linkedin","scheduled_date":"2026-12-05","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"Useful help begins by asking what is needed.","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"special","theme":"Reflection / volunteering","working_angle":"Useful help begins by asking what is needed.","angle_is_final_headline":false,"body_text":"A person can arrive ready to help and still make more work.\n\nAn organisation may need someone to finish an ordinary task on an ordinary Tuesday. A volunteer may arrive with an exciting idea, a camera and only Saturday afternoon available.\n\nNeither intention needs to be unkind. The needs do not yet meet.\n\nOn International Volunteer Day, asking what is useful can be a more respectful beginning than announcing what we want to offer.\n\nThe answer might be administrative work, a skill we have, or a small repeated commitment. It might be that this is not the right time. Accepting that answer is part of helping, too.\n\nThere are practical questions worth asking without turning generosity into a performance review. Who will explain the task? What can I reliably complete? Are there safeguarding or training requirements? If I stop, how much work will someone else inherit?\n\nReliability does not require unlimited availability. A clear two-hour commitment can be easier to use than a broad promise that keeps changing.\n\nPeople receiving help should keep their privacy, choices and dignity. Gratitude is not a fee they owe for our involvement.\n\nThe useful contribution may be less visible than the one we imagined. It is still a contribution if it answers the need rather than our wish to be seen answering it.\nhttps://www.un.org/en/observances/volunteer-day/background\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-05-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"Useful help starts with the need: ask, agree a commitment, complete it. Respect privacy and choice.","clearance":"pending"}],"sources":[{"title":"International Volunteer Day: Background","url":"https://www.un.org/en/observances/volunteer-day/background","publisher":"United Nations","accessed_date":"2026-11-14","note":"Annual5 December date; no current-year theme or estimates used."}],"reserve_fallback":false,"special_day":"International Volunteer Day","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.543351+00:00"},{"item_id":"li-2026-12-06-personal-one_piece","day_index":15,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Reflection","platform":"linkedin","scheduled_date":"2026-12-06","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"A pause need not justify itself by making us productive.","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"reflection","theme":"Reflection","working_angle":"A pause need not justify itself by making us productive.","angle_is_final_headline":false,"body_text":"We often defend a pause by explaining what it will help us do afterwards.\n\nRest so you can think better. Walk so you can return with an answer. Stop for a while so you can keep going.\n\nThose can be good reasons. They are not the only reasons a person is allowed to stop.\n\nA quiet afternoon does not become wasted because it produces no insight. A walk can remain a walk.\n\nAt the same time, a pause can be used to postpone a conversation that still needs to happen. The distinction is not visible from the outside. Two people sitting quietly may be doing very different things, and one person may not yet know which it is.\n\nA gentler question than \"Was this productive?\" might be: am I allowing myself a rest, or asking the rest to make a decision disappear?\n\nIf something needs attention, we can name a time to return to it. That boundary may make the pause more restful, not less.\n\nWe do not have to turn every ordinary hour into evidence of self-improvement. Some hours can be lived without being turned into a lesson.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-06-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"A pause can remain a pause. Rest. No insight required. Return when it is time.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.552378+00:00"},{"item_id":"li-2026-12-07-personal-daytime","day_index":16,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"AI / data quality","platform":"linkedin","scheduled_date":"2026-12-07","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"An empty box can tell five different stories.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"AI / data quality","working_angle":"An empty box can tell five different stories.","angle_is_final_headline":false,"body_text":"An empty box is not an answer.\n\nIt might mean the question was never asked. The answer was not known. The person chose not to disclose it. The question did not apply. Or the data failed to arrive.\n\nThose are different states. An AI system that receives only a blank may have no way to distinguish them.\n\nImagine a support assistant reading a customer record. A missing preference is treated as permission to choose. A missing inspection result is described as no fault found. A missing answer becomes an answer the system was never given.\n\nThis is a design example, not a claim about a particular model. The problem begins before the wording of its response: the input has discarded a distinction the decision needs.\n\nPreserving every possible reason for absence would make a system unwieldy. Preserve the reasons that change what the system is allowed to conclude or do.\n\nFor one field, unknown and not applicable may be enough. For another, declined to disclose needs its own treatment. The states should be meaningful to the people entering the data, not only convenient for the database.\n\nThen test the output. Does the system keep uncertainty visible, or quietly turn it into a default claim?\n\nA model cannot reliably respect a distinction our records have already erased.","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/missing-states.png","caption":"Original conceptual diagram, composed from text and vector shapes; illustrative, not measured data. No generative-image service used.","alt_text":"Five possible meanings of an empty field: not asked, unknown, not disclosed, not applicable, not received.","ai_origin_labelled":false,"clearance":"not_required"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"not_required_asserted","image_clearance_assertions":["not_required"],"scheduling_blocked":"","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-12-07-amtl_page-page","day_index":17,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Quantum","platform":"linkedin","scheduled_date":"2026-12-07","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Quantum faster than what, on which problem?","content_format":"LinkedIn image post","account":"amtl_page","slot":"daytime","slot_type":"post","theme":"Quantum","working_angle":"Quantum faster than what, on which problem?","angle_is_final_headline":false,"body_text":"\"Quantum is faster\" leaves out most of the comparison.\n\nFaster on which problem? At what size? To what quality of answer? Compared with which classical method? Does the timing include preparing inputs and interpreting results?\n\nIBM's quantum learning material distinguishes problems that are already straightforward for classical computers from candidates for quantum approaches. It also separates theoretical algorithms, practical heuristics and hardware limits.\n\nThat is a more useful starting point than treating quantum computing as a replacement for ordinary computing.\n\nFor a proposed experiment, write down the problem and a credible classical baseline before choosing the demonstration. Decide what result would count as useful and what evidence would change the team's view.\n\nA successful small experiment may establish that the approach works in that setting. It does not automatically establish a practical advantage at business scale. A negative result may still teach the team that its assumed bottleneck sits elsewhere.\n\nThere is room for curiosity without a premature return-on-investment claim. Learn the methods, examine the assumptions and keep the comparison fair.\n\nThe question is not whether quantum computing is impressive. It is what a particular method lets us do that the available alternatives do not.\nhttps://quantum.cloud.ibm.com/learning/en/courses/quantum-computing-in-practice/applications-of-qc\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-07-amtl_page-page-owner.png","caption":"Visual created with ChatGPT","alt_text":"Quantum faster than what? Compare problem, scale, answer quality and classical baseline. Compare the whole task.","clearance":"pending"}],"sources":[{"title":"Which problems are quantum computers good for?","url":"https://quantum.cloud.ibm.com/learning/en/courses/quantum-computing-in-practice/applications-of-qc","publisher":"IBM Quantum Learning","accessed_date":"2026-11-14","note":"Distinguishes easy classical problems, candidate applications, heuristics and hardware limits. No current performance milestone or speedup claimed."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.563353+00:00"},{"item_id":"li-2026-12-07-personal-evening","day_index":18,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Culture / reflection","platform":"linkedin","scheduled_date":"2026-12-07","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"A familiar song can carry a place we no longer inhabit.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Culture / reflection","working_angle":"A familiar song can carry a place we no longer inhabit.","angle_is_final_headline":false,"body_text":"A familiar song can make a place feel briefly close.\n\nNot because the place has returned. The room may have changed, the people may have moved, and the version of us who first heard it may be difficult to recognise now.\n\nWe can be moved by that closeness without treating memory as a faithful recording.\n\nThere is a temptation to let the feeling settle a larger argument: life was better then, people were kinder, everything since has been a decline. A song does not give us that evidence. It gives us a moment in which something feels present again.\n\nPerhaps that is enough.\n\nWe can ask what the feeling points towards. A language we have not spoken for a while. A place we might visit. An ordinary pleasure that needs no return to the past to be enjoyed now.\n\nNostalgia becomes a smaller burden when we stop asking it to rebuild an entire time. It can offer a thread rather than a destination.\n\nThe song will end. It need not leave us with a verdict on the present. It may simply leave us with something we still want to make room for.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-07-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"A memory can be a thread, not a verdict on the present.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.575705+00:00"},{"item_id":"li-2026-12-08-personal-daytime","day_index":19,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Cyber","platform":"linkedin","scheduled_date":"2026-12-08","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Who still holds the key after the contractor leaves?","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Cyber","working_angle":"Who still holds the key after the contractor leaves?","angle_is_final_headline":false,"body_text":"The contractor's account is disabled. A service they configured is still running with a shared credential.\n\nIn this hypothetical case, the visible offboarding step worked. The relationship between the person and the surviving access was never recorded.\n\nRemoving access is easier when we know what was granted and why. That includes more than a named login: service accounts, API tokens, shared mailboxes, delegated permissions and the authority to invite somebody else.\n\nNIST's zero trust architecture focuses on access to resources, rather than treating presence inside a network as sufficient trust. The same resource-level view helps ask a practical departure question: what can still be reached, through which identity, after this person leaves?\n\nDo not respond by revoking every credential without checking dependencies. A rushed removal can stop a service used by customers or other staff.\n\nInstead, assign an owner to each surviving access path, confirm its business purpose and replace or rotate credentials through the service's supported process. Check that necessary work continues and that the departing person's access no longer does.\n\nThe best time to make that record is when access is granted, while the reason is still clear.\n\nOffboarding should close a relationship with access. It should not begin an archaeological search for it.\nhttps://csrc.nist.gov/pubs/sp/800/207/final\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-08-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"Close the relationship with access: identity, resource, purpose and owner. Review what survives a departure.","clearance":"pending"}],"sources":[{"title":"Zero Trust Architecture, SP 800-207","url":"https://csrc.nist.gov/pubs/sp/800/207/final","publisher":"NIST","accessed_date":"2026-11-14","note":"Abstract separates authentication and authorisation and focuses on resources. Recovery/offboarding examples and maps are original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.585792+00:00"},{"item_id":"li-2026-12-08-personal-evening","day_index":20,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Reserve: responsible demonstrations","platform":"linkedin","scheduled_date":"2026-12-08","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"A useful demonstration can include the part that did not work.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"reserve","theme":"Reserve: responsible demonstrations","working_angle":"A useful demonstration can include the part that did not work.","angle_is_final_headline":false,"body_text":"The demonstration is smooth. Every input has been chosen to behave.\n\nThat can be a sensible way to introduce an unfamiliar idea. It becomes less useful when the audience is deciding whether to rely on it.\n\nImagine showing a tool that turns an untidy document into a clean summary. The ordinary example works. An ambiguous table does not. If the second example is left out, the audience may leave with the wrong picture of where review is needed.\n\nA demonstration does not need to be a public endurance test. Nor must every failure mean the tool is unsuitable. The useful question is whether the audience has seen enough to understand the boundary.\n\nShow a normal case, an awkward case and what happens when the system cannot finish. Explain which improvements are already working and leave unfinished capabilities out of the claim.\n\nThere is room to say, \"This part needs a person,\" without making it sound like an embarrassment.\n\nPeople can plan around a known limitation. They cannot plan around a limitation hidden by the choice of example.\n\nConfidence earned in a demonstration should survive the first ordinary day after it.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-08-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Show the boundary: ordinary case, awkward case and cannot finish. What should a person expect next?","clearance":"pending"}],"sources":[],"reserve_fallback":true,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.596247+00:00"},{"item_id":"li-2026-12-09-personal-daytime","day_index":21,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Business / continuity","platform":"linkedin","scheduled_date":"2026-12-09","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The policy covers the loss. Can the business survive the wait?","content_format":"LinkedIn long-form article","account":"personal","slot":"daytime","slot_type":"business_article","theme":"Business / continuity","working_angle":"The policy covers the loss. Can the business survive the wait?","angle_is_final_headline":false,"body_text":"A reimbursement can arrive after the cash is needed.\n\nImagine a small business whose premises become unusable. Assume, for the sake of the example, that an insurance policy covers a defined loss. Wages, temporary accommodation and supplier bills may still need to be funded while the claim is assessed.\n\nThis is a cash-timing example, not a statement about what any policy covers or when an insurer must pay. Those answers depend on the actual wording, circumstances and applicable rules.\n\nThe distinction is worth keeping: eventual recovery and immediate liquidity solve different problems.\n\nDraw the sequence, not only the total\n\nA business continuity conversation often begins with what can be recovered. Add a second question: when does money need to leave the business, and when could funds realistically become available?\n\nSeparate known due dates from assumptions. Do not put a hoped-for payment into the same category as money already available. A claim can be justified while its amount, evidence or timing remains unsettled.\n\nThe point is not to predict every delay. It is to identify which delay would make the present plan fail.\n\nRead the conditions while there is time to ask\n\nA policy may contain definitions, limits, exclusions and obligations that affect a particular claim. A broker or qualified adviser should explain how the actual wording applies. A generic checklist cannot replace that review.\n\nFor planning purposes, the business can still organise the documents and contacts it may need: policy details, asset records, relevant financial information and a way to reach the people responsible if the usual office systems are unavailable.\n\nKeeping records accessible is not the same as establishing coverage. It can make a difficult conversation less confused.\n\nConnect the financial plan to the operating plan\n\nA temporary location may require a deposit before trading resumes. A replacement system may need setup work before it produces revenue. A delayed restart can change both the cost and the expected receipts.\n\nThese are dependencies between operations and cash, not simply numbers for separate spreadsheets. Let the people responsible for each plan test the other's assumptions.\n\nUse questions rather than false certainty\n\nWhat must be paid first? Which costs can be deferred by agreement? Who can approve emergency spending? What would happen if the assumed receipt arrived later? Which options require a decision now to remain available?\n\nNone of those questions implies that borrowing, additional cover or a particular reserve level is the right answer. The right choice depends on the business and professional advice.\n\nA plan becomes more useful when it shows the period between disruption and recovery. That interval is where a covered loss can still become an operating crisis.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-09-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"A covered loss can still leave a cash gap: bills fall due, claim is assessed, funds may arrive later. Illustrative sequence, not policy advice.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.605628+00:00"},{"item_id":"li-2026-12-09-amtl_page-page","day_index":22,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"AI / knowledge maintenance","platform":"linkedin","scheduled_date":"2026-12-09","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"A correct answer can outlive the rule that made it correct.","content_format":"LinkedIn long-form article","account":"amtl_page","slot":"daytime","slot_type":"business_article","theme":"AI / knowledge maintenance","working_angle":"A correct answer can outlive the rule that made it correct.","angle_is_final_headline":false,"body_text":"The answer was correct when it was approved. The policy changed on Monday.\n\nA knowledge assistant can keep repeating an old answer with excellent grammar and a genuine citation. The remaining error is time.\n\nThis hypothetical case is different from inventing a source. The source exists and once supported the answer. It no longer describes the rule people should follow.\n\nGive knowledge a time boundary\n\nFor policy-dependent material, record which document is authoritative, when it took effect and who owns its maintenance. Where a review date or expiry is appropriate, make it operational rather than decorative.\n\nA review date does not prove that the text remains correct until then. It provides a point at which someone must check. A material change should trigger earlier review.\n\nNot every fact needs the same treatment. A historical account and a current approval threshold have different relationships with time. Concentrate on information whose age can change a decision.\n\nPreserve the distinction between current and historical\n\nPeople may legitimately ask what the rule was last year. Removing every old document can make that impossible. Mixing old and current documents without clear status creates the opposite problem.\n\nThe system needs to know whether it is answering a present operational question or a historical one. If the question is ambiguous and the difference affects an action, ask rather than silently selecting a period.\n\nArchive status, effective dates and version relationships should travel with the content into search and retrieval. A filename that happens to contain a year is a weak substitute.\n\nTest the transition, not only the answer\n\nCreate a safe test in which a fictional rule changes. Before the change, verify the old answer. After the change, ask the same operational question and a separate historical question. Check which source each answer uses.\n\nInclude cached summaries, copied FAQ entries and examples in training material. A policy can be updated in its home document while older explanations remain elsewhere.\n\nGive uncertainty an owner\n\nIf two documents disagree or an effective date cannot be established, the assistant should not manufacture a compromise. Identify the unresolved point and route it to the person responsible for the rule. The fallback should explain what remains unverified without exposing private material to the wrong audience.\n\nNIST's AI Risk Management Framework treats governance and ongoing measurement and management as continuing work. This review pattern applies that idea to the lifetime of an answer; it is not a NIST-prescribed checklist.\n\nA knowledge system needs a way to stop saying something that used to be true. Maintenance is part of the answer, not a task that begins after deployment.\nhttps://airc.nist.gov/airmf-resources/airmf/5-sec-core/","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/answer-lifetime.png","caption":"Original conceptual diagram, composed from text and vector shapes; illustrative, not measured data. No generative-image service used.","alt_text":"Old and new rules feed historical and current questions separately; unclear authority or period calls for a check.","ai_origin_labelled":false,"clearance":"not_required"}],"sources":[{"title":"AI RMF Core","url":"https://airc.nist.gov/airmf-resources/airmf/5-sec-core/","publisher":"NIST","accessed_date":"2026-11-14","note":"Governance, measurement and management are ongoing. Answer-lifetime review pattern is original, not a NIST-prescribed checklist."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"not_required_asserted","image_clearance_assertions":["not_required"],"scheduling_blocked":"","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-12-09-personal-evening","day_index":23,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Learning / everyday life","platform":"linkedin","scheduled_date":"2026-12-09","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"What did I miss? A question with room for an answer.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Learning / everyday life","working_angle":"What did I miss? A question with room for an answer.","angle_is_final_headline":false,"body_text":"\"What did I miss?\" can be an invitation. It can also be a challenge wearing a question mark.\n\nThe difference often arrives after the answer.\n\nIf every correction is met with a defence, people learn that the question was not an opening. It was a request to confirm that the speaker had already considered everything.\n\nNo one has to accept every criticism. A colleague may misunderstand the situation or recommend a change that would create another problem. Listening still requires enough room for their information to alter the discussion.\n\nOne small habit can help: before explaining why a suggestion will not work, say what new information it contains. \"I had not realised the deadline affects your team on Friday\" is different from preparing a rebuttal while the other person speaks.\n\nThen be clear about the decision. What will change? What will not? What needs another check?\n\nA question is not made sincere by its wording alone. It becomes sincere when an answer can have consequences.\n\nThere is a quiet kind of confidence in being willing to discover that the picture was incomplete.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-09-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"What did I miss? New information, changed understanding and a visible decision. An answer should be allowed to change shape.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.614438+00:00"},{"item_id":"li-2026-12-10-personal-daytime","day_index":24,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Business / procurement","platform":"linkedin","scheduled_date":"2026-12-10","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The tender is open. Eligibility started earlier.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Business / procurement","working_angle":"The tender is open. Eligibility started earlier.","angle_is_final_headline":false,"body_text":"The opportunity appears on Monday. One requirement needed preparation months ago.\n\nImagine a small supplier finding a tender that fits its work. The closing date leaves enough time to write a response. A required assurance, reference or qualification cannot be obtained that quickly.\n\nThe writing window was open. The eligibility window had effectively started earlier.\n\nThis is a planning example, not a statement that every tender requires the same credentials. Read the actual conditions. Distinguish mandatory requirements from evaluation preferences, and use the buyer's stated clarification process when something is unclear.\n\nThere is a practical lesson for business development. Review a sample of relevant opportunities before deciding which future requirements are worth preparing for. Do not buy every badge simply because it appears in a procurement document somewhere.\n\nAsk which markets the business genuinely wants to serve, which requirements recur there and what evidence would demonstrate capability. The preparation may involve doing different work, not merely documenting existing work more attractively.\n\nAlso decide when not to bid. A rushed response cannot repair a fundamental mismatch, and winning an obligation the business cannot fulfil is not a good outcome.\n\nOpportunity readiness is quieter than proposal writing. It is the work that lets a genuine choice exist when the notice arrives.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-10-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"The opportunity opens. Preparation started earlier. Capability, evidence, eligibility and response. Build the preparation before the window.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.623353+00:00"},{"item_id":"li-2026-12-10-personal-evening","day_index":25,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Human rights / dignity","platform":"linkedin","scheduled_date":"2026-12-10","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"Dignity should not depend on being easy to serve.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"special","theme":"Human rights / dignity","working_angle":"Dignity should not depend on being easy to serve.","angle_is_final_headline":false,"body_text":"A service is most revealing when the person does not fit its usual path.\n\nThey may need more time, another language, an accessible format or a way to explain something the form never anticipated.\n\nNone of that reduces their claim to be treated with dignity.\n\nHuman Rights Day marks the adoption of the Universal Declaration of Human Rights. Its starting point is not that rights are earned through convenience, confidence or the ability to complete our paperwork.\n\nA team cannot repair every injustice through a service design exercise. It can examine the choices within its control.\n\nWhen someone cannot use the standard route, is there another route? Can staff exercise judgement without making the person repeatedly disclose private information? Is a refusal explained clearly, with a way to question a mistake where appropriate?\n\nFair treatment does not always mean an identical process. Sometimes the same requirement imposes a very different burden on different people. Understanding that burden is part of deciding what is fair.\n\nThese questions do not replace legal duties or rights advice. They make a simpler demand of our everyday work: do not let a process's convenience become a measure of a person's worth.\n\nA respectful service should not reserve its best manners for the people it finds easiest to process.\nhttps://www.un.org/en/observances/human-rights-day\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-10-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Dignity is not a reward for convenience. A usable route, a clear explanation and a way to question a mistake.","clearance":"pending"}],"sources":[{"title":"Human Rights Day","url":"https://www.un.org/en/observances/human-rights-day","publisher":"United Nations","accessed_date":"2026-11-14","note":"10 December observance and UDHR origin. No annual theme, legal advice or sector-specific duty claimed."}],"reserve_fallback":false,"special_day":"Human Rights Day","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.631802+00:00"},{"item_id":"li-2026-12-11-personal-daytime","day_index":26,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Philosophy / responsibility","platform":"linkedin","scheduled_date":"2026-12-11","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Consistency can become an excuse to keep the wrong promise.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Philosophy / responsibility","working_angle":"Consistency can become an excuse to keep the wrong promise.","angle_is_final_headline":false,"body_text":"\"I said I would\" is usually a good reason to follow through.\n\nIt is not a reason to ignore what has changed.\n\nImagine agreeing to finish a task in a particular way, then discovering that the approach will cause avoidable harm. There are two responsibilities now: take the original promise seriously and respond honestly to the new information.\n\nQuietly abandoning the promise fails the first. Carrying it out without telling anyone fails the second.\n\nA better response may be to return to the person who relied on it. Explain what changed, what the original commitment would now involve and what alternative you can offer. They should not have to discover your revised understanding through the consequences.\n\nSome promises deserve to survive discomfort. Others were made on assumptions that no longer hold. Telling the difference requires judgement, not a slogan about always keeping your word or always changing your mind.\n\nPerhaps consistency is less about repeating the same action and more about staying answerable for the reasons behind it.\n\nChanging a commitment can be responsible. Making the change visible is part of the responsibility.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-11-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"What changed? Who relied on the promise, what alternative can I offer, and what needs explaining? Make the change visible.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.640363+00:00"},{"item_id":"li-2026-12-11-amtl_page-page","day_index":27,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Cyber / evidence","platform":"linkedin","scheduled_date":"2026-12-11","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Security evidence needs a source and a period.","content_format":"LinkedIn image post","account":"amtl_page","slot":"daytime","slot_type":"post","theme":"Cyber / evidence","working_angle":"Security evidence needs a source and a period.","angle_is_final_headline":false,"body_text":"A screenshot shows a control switched on. It does not show how long it has been on, which systems it covers or whether it works.\n\nThat makes the screenshot limited evidence, not useless evidence.\n\nA useful review separates a claim from the material supporting it. For each claim, record the scope, observation period, source, check performed and any limitation. These are suggested working fields, not a certification standard.\n\n\"This setting was enabled in this account when checked today\" is a different claim from \"this control operated across every relevant system throughout the quarter\". The second needs evidence the first screenshot cannot provide.\n\nWhere sampling is used, describe what was sampled and what was not. Where a test cannot be performed safely, name the missing check rather than quietly treating it as passed.\n\nEvidence also ages. A configuration change, new service or altered process can make an earlier conclusion incomplete before the next scheduled review.\n\nThe goal is not an archive so large that nobody can question it. It is a trail another person can follow from the claim to the check, with the uncertainty still visible.\n\nA smaller defensible claim is more useful than a broad assurance that asks the reader to fill in the gaps.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-11-amtl_page-page-owner.png","caption":"Visual created with ChatGPT","alt_text":"What does the evidence establish? Claim, scope, period, source and limitation.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.648752+00:00"},{"item_id":"li-2026-12-11-personal-evening","day_index":28,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Literature / quote note","platform":"linkedin","scheduled_date":"2026-12-11","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"Understanding a character is not excusing them.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Literature / quote note","working_angle":"Understanding a character is not excusing them.","angle_is_final_headline":false,"body_text":"\"Mankind was my business.\"\n\nMarley's ghost says this in Charles Dickens's A Christmas Carol. It answers Scrooge's attempt to describe him as a good man of business.\n\nThe exchange changes the meaning of that praise. Competence within a narrow definition of work is being judged against a wider responsibility.\n\nReading the scene does not require us to believe that every commercial task must solve every social problem. It asks us to notice what a person has excluded from the word \"business\" in order to feel satisfied with a life.\n\nA novel can let us understand how a character became narrow without asking us to approve of the narrowness. Explanation gives the judgement more detail. It does not have to cancel it.\n\nThe same distinction can make reading more interesting. Instead of deciding immediately whether a character is good or bad, follow what they notice, what they avoid and who pays for the things they choose not to see.\n\nWe can recognise something human in a character and still want them to change.\n\nPerhaps that is one of fiction's useful freedoms: it gives us time to understand an action without requiring us to call it acceptable.\nhttps://www.gutenberg.org/cache/epub/46/pg46.txt\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-11-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Still examine the action, and still examine the reasons. Two overlapping questions.","clearance":"pending"}],"sources":[{"title":"A Christmas Carol","url":"https://www.gutenberg.org/cache/epub/46/pg46.txt","publisher":"Project Gutenberg / Charles Dickens","accessed_date":"2026-11-14","note":"StaveOne, Marley speaks to Scrooge. Short quotation and original literary interpretation."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.656732+00:00"},{"item_id":"li-2026-12-12-personal-one_piece","day_index":29,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Reflection","platform":"linkedin","scheduled_date":"2026-12-12","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"What was worth keeping from the week?","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"reflection","theme":"Reflection","working_angle":"What was worth keeping from the week?","angle_is_final_headline":false,"body_text":"The week does not need a score.\n\nThere may be something worth keeping from it: a phrase that helped, a meal enjoyed slowly, a task finally made simpler, a conversation that left more room than it took.\n\nNot everything valuable announces itself as progress. Some things are only recognisable because we would like to make room for them again.\n\nThat is a different question from whether we made the most of the week. \"The most\" can turn an ordinary life into a competition with an imaginary better-managed one.\n\nWhat was worth keeping is smaller. It permits an uneven week to contain something good without requiring us to relabel the difficult parts as gifts.\n\nWe can also leave something behind: an unnecessary argument, a standard nobody asked us to meet, the thought that every available hour should have been used better.\n\nThere need not be a plan at the end of the reflection. Sometimes noticing is enough. If something does deserve a place next week, make that place small enough to be real.\n\nA life is partly shaped by what we repeat. We can choose a little of that repetition with care.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-12-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"What was worth keeping? Notice it, make a little room and repeat with care.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.665173+00:00"},{"item_id":"li-2026-12-13-personal-one_piece","day_index":30,"content_pack":"LinkedIn weeks three and four - owner approved31to60","domain":"Reflection","platform":"linkedin","scheduled_date":"2026-12-13","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"Enough need not mean the same thing every Sunday.","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"reflection","theme":"Reflection","working_angle":"Enough need not mean the same thing every Sunday.","angle_is_final_headline":false,"body_text":"Enough is a difficult word to use when the list can always grow.\n\nThere is another message to answer, another room to tidy, another useful thing we could learn. Finishing everything is not always available as a stopping rule.\n\nWe might need a different one.\n\nWhat genuinely needs attention today? What can wait without passing an unfair burden to somebody else? What are we continuing only because stopping feels uncomfortable?\n\nThe answers will change. A quiet Sunday and a demanding one do not need to resemble each other to be well lived.\n\nEnough should not become another strict standard. There are days when we do less than we hoped and days when circumstances ask more than we wanted to give. Neither tells the whole story of a person.\n\nPerhaps the word is useful because it lets a day have an edge. Beyond that edge, we are not required to keep proving that we have earned the evening.\n\nAn unfinished list can wait. The day is still allowed to end.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-12-13-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"The day can have an edge: necessary today or can wait. No need to earn the evening.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:58:49 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"LinkedIn weeks three and four.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwNjFEMTg0MzJFMjkzMDdDNTZGAA==","reference":"Review31-60approvedaswritten14November2026at11:58:49Australia/Sydney."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.673768+00:00"}],"filtered_item_count":30,"spark_packet":{},"ripple_packet":{}},{"id":4,"plan_id":"social-calendar-import-linkedin-first-two-weeks-owner-approved-28fe3d7ab6dbe70905b74af2c2092985005d3003a90bcd79ad80d54f507fd913","pack_name":"LinkedIn first two weeks - owner approved","domain":"mixed","platform":"linkedin","start_date":"2026-11-16","posting_time":"per-item","timezone":"Australia/Sydney","item_count":30,"artifact_dir":"","external_publish_performed":false,"target_app_write_performed":false,"human_review_required":true,"created_at":"2026-11-14T18:19:49.204069+00:00","receipt_hash":"9d16a2a47eee2651308c48bc3061705b020478892ec3d91d68d451ce3ac0b57f","customer_id":"amtl","archived":false,"archive_note":"","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","schedule":[{"item_id":"li-2026-11-16-personal-daytime","day_index":1,"content_pack":"LinkedIn first two weeks - owner approved","domain":"AI","platform":"linkedin","scheduled_date":"2026-11-16","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The link opened. The evidence did not.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"AI","working_angle":"The link opened. The evidence did not.","angle_is_final_headline":false,"body_text":"An AI answer gives you a link. You open it. The page is real.\n\nThat settles one question: the page exists.\n\nIt does not settle whether the page supports the answer.\n\nImagine a report claiming that a new working pattern improved productivity by 20%. Its link leads to a real study. But the study measured how quickly volunteers finished one writing task. It did not measure a company's productivity.\n\nThe source is genuine. The claim has grown on the way out.\n\nThis is easy to miss because a citation lends an answer the appearance of having been checked. Yet several different checks are hiding inside that small footnote.\n\nDoes the source say this? Were these the people and conditions it studied? Does the result support a decision here, or only a question worth testing?\n\nNIST's generative AI risk profile warns that AI outputs can include false logic or citations that appear to justify an answer. A real citation still needs a separate check: the connection between its evidence and our sentence.\n\nA reviewer might write: \"The study supports faster completion of this task in this setting. It does not establish a 20% improvement across the business.\"\n\nThe smaller claim is not a weaker version of the larger one. It is the claim we can defend.\n\nWe do not need to turn every quick answer into a research project. We do need to recognise the sentence on which a decision rests. Check that sentence first. Open its source. Find the passage that supports it. Read enough around it to see what was left out.\n\nIf the source supports less than we wrote, write less.\n\nA source should limit our confidence as well as lend us some.\nhttps://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/evidence-gates.png","caption":"Image: created with AI using ArtCraft. Original conceptual framework, not measured data.","alt_text":"Four evidence gates: source exists, claim supported, context fits, action justified.","ai_origin_labelled":true,"clearance":"cleared"}],"sources":[{"title":"Generative Artificial Intelligence Profile","url":"https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf","publisher":"NIST","accessed_date":"2026-11-14","note":"Section 2.2 supports false logic/citation risk; fictional 20%example is not a study result."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"pending","image_clearance_assertions":["cleared"],"scheduling_blocked":"image_clearance_pending","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-11-16-amtl_page-ai","day_index":2,"content_pack":"LinkedIn first two weeks - owner approved","domain":"AI","platform":"linkedin","scheduled_date":"2026-11-16","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"What an AI-use register should help a person decide.","content_format":"LinkedIn long-form article","account":"amtl_page","slot":"","slot_type":"business_article","theme":"AI","working_angle":"What an AI-use register should help a person decide.","angle_is_final_headline":false,"body_text":"What should an AI-use register help a person decide?\n\nA register can be accurate and still be difficult to use. Imagine a list containing the name of every AI tool in an organisation. The list is complete. A colleague asks whether they can use one of those tools to summarise a confidential document. The register has no answer.\n\nThe missing information is not another product name. It is the connection between the system and the work people want to do with it.\n\nStart with a use, not a logo\n\nThe same tool might help someone rewrite public text and help someone else assess an application. Those uses can involve different information, different people and different consequences. One row per supplier can hide those differences.\n\nNIST's AI Risk Management Framework includes maintaining an inventory of AI systems under GOVERN 1.6. MAP 1.1 asks for intended purposes, users and deployment context to be understood. The framework does not prescribe the register below. It supports the reason for moving beyond a list of names.\n\nAn original practical design is to make each entry useful to someone at the point of a decision. Describe the use in ordinary words. Name an accountable owner. State what information may enter the system, what the output may support and what it must not decide by itself. Link to the evidence used for that boundary and give the entry a review date.\n\nSeparate permission from description\n\n\"The team uses it\" is a descriptive fact. \"The team is authorised to use it for this purpose\" is a different claim. A register that mixes them can make discovery look like approval.\n\nKeep the states visible. A newly found use can be recorded without being endorsed. A reviewed use can carry explicit limits. A retired use should not disappear so completely that another team mistakes it for a new discovery.\n\nFor example, an entry might say a tool is approved for summarising public consultation documents, but not for making eligibility decisions. This is a hypothetical boundary, not a recommendation about a named system. Its value is that the next person can see what the previous review did and did not establish.\n\nTest the register with a question\n\nTake one ordinary request from a colleague. Can they find the applicable use, the allowed information, the person who can resolve an exception and the date of the last review?\n\nIf not, adding another column may not help. The descriptions may be too broad, the ownership unclear or the decision itself unresolved.\n\nA useful register does not promise that every risk has been settled. It makes the unsettled parts easier to find before someone acts.\n\nSource: NIST AI RMF 1.0, GOVERN 1.6 and MAP 1.1. The register design is an original proposal, not a claim of certification or compliance.\nhttps://airc.nist.gov/airmf-resources/airmf/5-sec-core/","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/ai-boundary.png","caption":"Image: created with AI using ArtCraft, with local text corrections. Original conceptual framework, not measured data.","alt_text":"Four panels record purpose, allowed information, decision owner and review date, with distinct discovery, review and retirement states.","ai_origin_labelled":true,"clearance":"cleared"}],"sources":[{"title":"AI RMF 1.0 Core","url":"https://airc.nist.gov/airmf-resources/airmf/5-sec-core/","publisher":"NIST","accessed_date":"2026-11-14","note":"GOVERN 1.6, 3.2; MAP 1.1, 3.5. Original workflows are not prescribed checklists or certifications."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"pending","image_clearance_assertions":["cleared"],"scheduling_blocked":"image_clearance_pending","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-11-16-personal-evening","day_index":3,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Culture / language","platform":"linkedin","scheduled_date":"2026-11-16","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"Many hands make light work. Which work?","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Culture / language","working_angle":"Many hands make light work. Which work?","angle_is_final_headline":false,"body_text":"\"Many hands make light work.\"\n\nTry moving a heavy table alone. The advice earns its place.\n\nNow imagine twelve people trying to agree on the last sentence of a wedding invitation.\n\nMore hands. Perhaps less lightness.\n\nThe proverb has not failed. We have asked it to travel without its conditions.\n\nSome work divides well. Carry this end. Pack those books. Check these figures. An extra person can take a useful part without changing what the others are doing.\n\nOther work needs the parts to become one choice. Someone must decide which sentence stays, when the invitation is finished and whose judgement settles a disagreement.\n\nMore help can be welcome in both situations. The arrangement has to be different.\n\n\"Too many cooks spoil the broth\" is not a reason to send everyone home. It is a reminder that contributions need to fit together.\n\nWe inherit sayings because they save us from learning everything again. The saving disappears when we stop asking where the advice fits.\n\nBefore repeating a familiar rule, try one extra question:\n\nWhat would have to be true for this to help?\n\nIt makes room for experience without asking experience to speak for every situation.\nhttps://www.dictionary.com/browse/many-hands-make-light-work","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/coordination-map.png","caption":"Image: created with AI using ArtCraft. Original conceptual framework, not measured data.","alt_text":"Coordination decision map by task divisibility and cost of disagreement.","ai_origin_labelled":true,"clearance":"cleared"}],"sources":[{"title":"Many hands make light work","url":"https://www.dictionary.com/browse/many-hands-make-light-work","publisher":"Dictionary.com","accessed_date":"2026-11-14","note":"Traditional proverb and converse; no single author or research attribution."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"pending","image_clearance_assertions":["cleared"],"scheduling_blocked":"image_clearance_pending","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-11-17-personal-daytime","day_index":4,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Cyber","platform":"linkedin","scheduled_date":"2026-11-17","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The warning was real. So were the interruptions before it.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Cyber","working_angle":"The warning was real. So were the interruptions before it.","angle_is_final_headline":false,"body_text":"The warning was real. So were the interruptions before it.\n\nA person dismisses a security warning. It is tempting to stop the explanation there: they should have paid attention.\n\nBut what has the system taught them to pay attention to?\n\nImagine a working day filled with notices that look equally urgent. Some require action. Some repeat yesterday's message. Others offer no useful choice. The person still has a job to finish.\n\nNIST's 2016 qualitative research described security fatigue among the people it interviewed. That is not a measure of every workplace today. It is a useful warning against designing security as an unlimited claim on human attention.\n\nThe answer is not to hide a serious alert. It is to stop making every interruption compete in the same voice.\n\nA useful warning should make a few things clear: what happened, what the person should do now, and where to go if they cannot safely decide. If the system already knows the safe action, ask why the user must keep discovering it.\n\nWe should still examine the decision that went wrong. We should also examine the decisions we made routine.\n\nBefore adding another warning, remove one that has taught people nothing.\n\nSource: NIST, Security Fatigue (2016).\nhttps://www.nist.gov/news-events/news/2016/10/security-fatigue-can-cause-computer-users-feel-hopeless-and-act-recklessly","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/alert-decision.png","caption":"Image: created with AI using ArtCraft. Original conceptual framework, not measured data.","alt_text":"A branching checklist distinguishes useful urgent decisions from non-interrupting information.","ai_origin_labelled":true,"clearance":"cleared"}],"sources":[{"title":"Security Fatigue","url":"https://www.nist.gov/news-events/news/2016/10/security-fatigue-can-cause-computer-users-feel-hopeless-and-act-recklessly","publisher":"NIST","accessed_date":"2026-11-14","note":"2016 qualitative interviews, not current population prevalence or measured effect of 50 interruptions."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"pending","image_clearance_assertions":["cleared"],"scheduling_blocked":"image_clearance_pending","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-11-17-personal-evening","day_index":5,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Reserve: timely new item","platform":"linkedin","scheduled_date":"2026-11-17","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"The easiest improvement may be the thing we stop asking for.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"reserve","theme":"Reserve: timely new item","working_angle":"The easiest improvement may be the thing we stop asking for.","angle_is_final_headline":false,"body_text":"The easiest improvement may be the thing we stop asking for.\n\nImagine a form with a field nobody can explain. It takes only a few seconds to complete. That sounds too small to investigate.\n\nYet someone must work out the answer, someone may have to correct it, and someone else may assume it has a purpose because it appears on the form.\n\nA small request can acquire authority simply by surviving.\n\nBefore making the field easier to fill, ask what decision uses the answer. If there is no decision, no obligation and no useful record to preserve, perhaps the improvement is deletion.\n\nThat does not mean removing every inconvenient question. Some questions protect people who are not in the room. The reason for keeping one should be as clear as the reason for removing it.\n\nEfficiency can begin as a polite refusal to keep handing a tiny unexplained task to the next person.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-17-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Before adding another field: what decision uses this answer, is it required, and can it be removed safely? Make the reason visible.","clearance":"pending"}],"sources":[],"reserve_fallback":true,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.220591+00:00"},{"item_id":"li-2026-11-18-personal-daytime","day_index":6,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Business","platform":"linkedin","scheduled_date":"2026-11-18","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The discount was visible. The extra promises were not.","content_format":"LinkedIn long-form article","account":"personal","slot":"daytime","slot_type":"business_article","theme":"Business","working_angle":"The discount was visible. The extra promises were not.","angle_is_final_headline":false,"body_text":"The customer asks for a discount. Someone checks the margin. The number still looks acceptable, so the order goes ahead.\n\nThen the small promises begin.\n\nCould we deliver on two dates instead of one? Use the customer's spreadsheet? Hold a second induction? Send a separate report to each branch?\n\nEach request sounds reasonable. Each person says yes to a different piece of it. Nobody has agreed to the whole job that now exists.\n\nBy the time the job is finished, the discount may be the easiest cost to explain.\n\nConsider a fictional order. After the normal direct costs, it has 100 units left to contribute towards overheads and profit. A discount takes 10. Extra work then uses another 35.\n\nThe business discussed the 10. Did anyone see the 35 being committed?\n\nThese are illustrative units, not a benchmark or an account of a real customer. They simply show why a price decision and a delivery decision cannot always be separated.\n\nA promise has to land somewhere\n\nWe often talk about exceptions as if they were little departures from a rule.\n\nFor the person delivering the service, an exception may be a second set of instructions, a different deadline or a new place where an error can occur.\n\nIt can also become a lasting expectation. The customer remembers that the report arrived by Friday. The person who agreed to it may remember it as a one-off favour.\n\nNow the next order begins with two different understandings of what was sold.\n\nThe hidden cost is not always waste\n\nIt would be a mistake to conclude that every exception should be refused.\n\nAn adjustment may make the service usable for a customer who would otherwise be excluded. A special requirement may reveal a genuine new market. A little extra work may be the right response to a failure we caused.\n\nThe question is whether we chose the work, whether the people doing it were part of that choice, and what we expected to learn from it.\n\nThere is also a useful distinction between valuable variation and avoidable repair. Helping someone access a service is not the same as retyping information because our own forms disagree.\n\nThe American Society for Quality separates prevention, appraisal, internal failure and external failure costs. That framework is about quality-related costs, not every cost of customisation. It is still a useful reminder to ask what kind of cost we are seeing before cutting it.\n\nIf we call all extra effort \"customer service\", we may protect recurring rework from examination. If we call it all \"inefficiency\", we may remove the adjustment that made the service humane.\n\nGive a promise a shape\n\nBefore agreeing to an exception, try recording five things in ordinary language.\n\nWhat changes? Who will do it? What does it cost in time or capacity? When does it end? Who can decide whether to repeat it?\n\nThis need not become another approval maze. A small, reversible request should have a light path. An ongoing commitment that changes another team's work deserves that team's involvement.\n\nThe record should travel with the job, not live in the inbox of the person who won the sale.\n\nOtherwise delivery meets the promise only after the customer expects it.\n\nLearn without making the customer the problem\n\nAfter the job, compare the work assumed with the work actually required.\n\nWhich extra steps helped the customer? Which repaired a defect? Which existed because we had not asked a necessary question at the start?\n\nA recurring exception deserves a design decision. Make it part of the service and resource it, offer it separately, improve the process that creates it, or stop promising it. Repeatedly calling it a one-off leaves the choice with whoever is tired enough to absorb the work.\n\nThe aim is not to make every customer identical. It is to stop making invisible promises about a business's limited time.\n\nThe next margin review could begin with a different question.\n\nNot only: what discount did we give?\n\nAlso: what work did we promise, and who knew we had promised it?\nhttps://asq.org/quality-resources/cost-of-quality","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/exception-lifecycle.png","caption":"Image: created with AI using ArtCraft. Original conceptual framework, not measured data.","alt_text":"New request receives owner, limit and review date, then a deliberate service decision.","ai_origin_labelled":true,"clearance":"cleared"}],"sources":[{"title":"Cost of Quality","url":"https://asq.org/quality-resources/cost-of-quality","publisher":"ASQ","accessed_date":"2026-11-14","note":"Prevention, appraisal, internal/external failure distinctions only. Commercial example and checks are original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"pending","image_clearance_assertions":["cleared"],"scheduling_blocked":"image_clearance_pending","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-11-18-amtl_page-cyber","day_index":7,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Cyber","platform":"linkedin","scheduled_date":"2026-11-18","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"What should a useful security exception record?","content_format":"LinkedIn image post","account":"amtl_page","slot":"","slot_type":"post","theme":"Cyber","working_angle":"What should a useful security exception record?","angle_is_final_headline":false,"body_text":"A security exception needs more than an expiry date.\n\nImagine an older system cannot meet a required control until a dependency changes. The gap is real. Recording it should make the decision clearer, not make the risk look settled.\n\nStart with the missing control and the use it affects. Name who owns the service and who is authorised to accept the risk. Those may be different people.\n\nThen record the temporary safeguards, the evidence that they operate, and the event that would force an early review. A failed safeguard should not have to wait for next month's meeting.\n\nFinally, state what would close the exception. If that depends on an unfunded project or a supplier date nobody has confirmed, keep the uncertainty visible.\n\nAt renewal, look for a changed decision rather than a changed timestamp. Has the gap narrowed? Has the exposure changed? Has someone with the right authority consciously accepted the continuing risk?\n\nNIST CSF 2.0 provides risk-response and governance outcomes. These suggested fields are an original design, not a prescribed form or compliance guarantee.\n\nA record can expose a difficult decision. It cannot authorise one by itself.\n\nSource: NIST Cybersecurity Framework 2.0.\nhttps://nvlpubs.nist.gov/nistpubs/cswp/nist.cswp.29.pdf\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-18-amtl_page-cyber-owner.png","caption":"Visual created with ChatGPT","alt_text":"Give an exception a boundary: gap, authority, safeguard, review trigger and closure condition. A renewal is a decision, not a date change.","clearance":"pending"}],"sources":[{"title":"Cybersecurity Framework 2.0","url":"https://nvlpubs.nist.gov/nistpubs/cswp/nist.cswp.29.pdf","publisher":"NIST","accessed_date":"2026-11-14","note":"High-level risk response and governance outcomes; exception template original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.232959+00:00"},{"item_id":"li-2026-11-18-personal-evening","day_index":8,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Learning / everyday life","platform":"linkedin","scheduled_date":"2026-11-18","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"The new colleague asked what we had stopped hearing.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Learning / everyday life","working_angle":"The new colleague asked what we had stopped hearing.","angle_is_final_headline":false,"body_text":"The new colleague asks why there are two lists.\n\nOne is for the weekly meeting. The other is for the people doing the work.\n\nEveryone knows that. It takes a newcomer to hear how odd it sounds.\n\nThis is an imagined scene, but the question is useful. Familiarity can make a workaround feel like part of the job rather than evidence that the job needs attention.\n\nThe new person does not automatically have the better answer. They may not yet understand the constraint, the history or the failure that led to the second list.\n\nThat is why a good response is neither \"we have always done it this way\" nor \"let us change it immediately\".\n\nTry: \"This is the problem it was meant to solve. Is that problem still here?\"\n\nNow experience has something to teach, and curiosity has somewhere to go.\n\nWe often ask new colleagues to learn our language quickly. It may be worth listening before they become fluent enough to stop asking.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-18-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Before defending a workaround, ask what problem created it, whether that problem remains, and which constraint remains. Experience explains. Curiosity tests.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.242938+00:00"},{"item_id":"li-2026-11-19-personal-daytime","day_index":9,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Business","platform":"linkedin","scheduled_date":"2026-11-19","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The invoice is correct. The customer still cannot pay.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Business","working_angle":"The invoice is correct. The customer still cannot pay.","angle_is_final_headline":false,"body_text":"The invoice is correct. The customer still cannot pay it.\n\nImagine that the price, tax and total are all right. But the customer's purchasing system needs a reference that never reached the invoice. Accounts sends it back. Sales says delivery is finished. The customer becomes the courier between two teams.\n\nA correct document has become an incomplete service.\n\nThis is a fictional example, not a claim about a particular business or a legal invoicing rule. It exposes a useful difference: accuracy inside a step is not the same as usability at the next step.\n\nBefore changing the invoice template, trace the missing reference. Who first knows it? Who can check it? Where should it travel with the job?\n\nAsking accounts to repair every omission may make the last step faster while leaving the cause untouched.\n\nThe test is simple enough to perform with one recent job: can the next person use what we hand them without reconstructing what we already knew?\n\nA handover is finished when the next person can begin, not when we can prove we sent something.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-19-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"Can the next person begin? Known at source, travels with the job, usable at the next step. Sent is not the same as usable.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.252830+00:00"},{"item_id":"li-2026-11-19-personal-evening","day_index":10,"content_pack":"LinkedIn first two weeks - owner approved","domain":"World Philosophy Day","platform":"linkedin","scheduled_date":"2026-11-19","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"A good question need not become an argument.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"special","theme":"World Philosophy Day","working_angle":"A good question need not become an argument.","angle_is_final_headline":false,"body_text":"A good question need not become an argument.\n\n\"What would change your mind?\"\n\nAsked with interest, it opens a conversation. Asked as a challenge, it can sound like a demand to surrender.\n\nThe words are identical. The relationship between the speakers is not.\n\nWorld Philosophy Day is a useful excuse to practise something quieter than winning a debate: making a belief easier to examine.\n\nStart with our own. What are we assuming? What experience might we be missing? Which part is a fact, which part a value, and which part a prediction about what will happen?\n\nDisagreement does not always disappear when those differences become clear. Sometimes we discover that we want different things. That is still progress over arguing about a number when the disagreement is about fairness.\n\nWe do not have to treat every view as equally well supported. We can ask for evidence without treating the person as an obstacle.\n\nPerhaps a conversation has gone well when both people can state the disagreement more honestly than they could at the start.\n\nWorld Philosophy Day: 19 November 2026. Date source: United Nations. The reflection is original.\nhttps://www.un.org/en/observances/world-philosophy-day\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-19-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Name the disagreement: fact asks what is true, value asks what is important, prediction asks what happens next. Different disagreements need different questions.","clearance":"pending"}],"sources":[{"title":"World Philosophy Day","url":"https://www.un.org/en/observances/world-philosophy-day","publisher":"United Nations","accessed_date":"2026-11-14","note":"Date 19 November 2026 verified; reflection original."}],"reserve_fallback":false,"special_day":"World Philosophy Day","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.263673+00:00"},{"item_id":"li-2026-11-20-personal-daytime","day_index":11,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Philosophy / personal development","platform":"linkedin","scheduled_date":"2026-11-20","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Can I change a belief without losing my footing?","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Philosophy / personal development","working_angle":"Can I change a belief without losing my footing?","angle_is_final_headline":false,"body_text":"Can I change a belief without losing my footing?\n\nThere is a difference between saying \"I was wrong about this\" and deciding \"I cannot trust myself about anything\".\n\nThe first revises a judgement. The second turns a correction into a verdict on the person making it.\n\nImagine learning that an argument you repeated left out an important exception. You can acknowledge the omission, correct the words and explain what changed. None of that requires pretending the earlier confidence never existed.\n\nIt does require giving up the comfort of looking consistent.\n\nConsistency has a useful place. People should be able to rely on our promises. But a promise and a prediction are different things. Keeping a promise can be honourable. Keeping a prediction unchanged after its basis has failed is something else.\n\nA small practice may help: name the part that changed and the part that did not.\n\n\"I still care about the outcome. I no longer think this is the best way to reach it.\"\n\nThat leaves a person standing somewhere more solid than either stubbornness or self-reproach.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-20-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"Keep the aim. Recheck the route. What I thought, what I now know, and what I will change. A correction need not be a verdict on the person.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.273272+00:00"},{"item_id":"li-2026-11-20-amtl_page-process","day_index":12,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Process","platform":"linkedin","scheduled_date":"2026-11-20","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Where a customer journey loses its owner.","content_format":"LinkedIn long-form article","account":"amtl_page","slot":"","slot_type":"business_article","theme":"Process","working_angle":"Where a customer journey loses its owner.","angle_is_final_headline":false,"body_text":"Where does a customer journey lose its owner?\n\nImagine a customer asking for help. The first team responds quickly and sends the request to a specialist. The specialist sends it to another department. Every transfer is recorded. Every team can show that it acted.\n\nThe customer still has to ask what happens next.\n\nThis is a fictional service journey, not a report about a named organisation. It is useful because failure does not require anyone to be careless. A process can divide responsibility so neatly that nobody owns the space between the parts.\n\nSeparate movement from acceptance\n\nA sent email proves that a message left one place. It does not prove that another team has accepted the work, understands the request or can act on it.\n\nThe UK Government Service Standard asks teams to solve a whole problem for users and work across organisational boundaries. It also warns against making services too broad and complicated. End-to-end ownership does not require one giant team. It requires the joins to work.\n\nOne practical design is to distinguish \"sent\" from \"accepted\". The receiving team confirms that it has enough information and the authority to take the next step. If it does not, the request should have a visible route back, not disappear into a new queue.\n\nGive uncertainty a home\n\nA handover can fail because nobody knows what to tell the customer while two teams resolve a boundary. Naming a contact for that period can be more useful than adding another status code.\n\nThat contact need not personally perform every task. Their job is to keep the whole request intelligible: who has it, what is missing and when the customer should expect another answer. Do not promise a deadline the receiving team has not accepted.\n\nFollow one request\n\nA useful review does not have to begin with a full process redesign. Follow one representative request, using information you are authorised to inspect. At each transfer, ask who believes they own the next action and what the customer has been told.\n\nIf those answers disagree, the gap is already visible. Fix the join and test it again before declaring the journey repaired.\n\nA customer should not need to understand the organisation chart to discover who is helping them. An internal transfer should reduce their work, not recruit them into coordinating ours.\n\nSource: GOV.UK Service Standard, point 2. The acceptance/contact model is an original proposal.\nhttps://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-20-amtl_page-process-owner.png","caption":"Visual created with ChatGPT","alt_text":"A handover has three states: sent, accepted and ready to act. Who owns the request between the states?","clearance":"pending"}],"sources":[{"title":"Solve a whole problem for users","url":"https://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem","publisher":"UK Government Digital Service","accessed_date":"2026-11-14","note":"End-to-end service design only, not legal portability requirements or invoicing law."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.283378+00:00"},{"item_id":"li-2026-11-20-personal-evening","day_index":13,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Literature / quote note","platform":"linkedin","scheduled_date":"2026-11-20","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"A map helps us see, then tells us what to miss.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"quote_note","theme":"Literature / quote note","working_angle":"A map helps us see, then tells us what to miss.","angle_is_final_headline":false,"body_text":"A map helps us see. It also chooses what we do not see.\n\nIn Lewis Carroll's The Hunting of the Snark, the crew celebrates a map that is \"A perfect and absolute blank!\"\n\nIt is a lovely joke. Nothing on the map can confuse them. Nothing can help them either.\n\nA useful map must leave things out. We would struggle to use one that reproduced every stone and shopfront. The question is which details it leaves out for the journey we intend to make.\n\nA road map can be excellent for a driver and poor for someone looking for a safe walking route. Neither traveller needs the whole world. They need different parts of it.\n\nOur summaries, dashboards and explanations make similar choices. Their neatness is not proof that the missing detail was unimportant.\n\nBefore admiring a clear picture, ask who needs to act on it. What would they fail to notice if this were all they could see?\n\nClarity is a responsibility to the reader, not an excuse to remove what makes the decision difficult.\n\nSource: Lewis Carroll, The Hunting of the Snark, Fit the Second. Interpretation is original.\nhttps://www.gutenberg.org/files/13/13-h/13-h.htm\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-20-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Choose the map for the journey. Who must act, what must they see, and what can be left out? A clear picture can still omit the decision.","clearance":"pending"}],"sources":[{"title":"The Hunting of the Snark","url":"https://www.gutenberg.org/files/13/13-h/13-h.htm","publisher":"Project Gutenberg / Lewis Carroll","accessed_date":"2026-11-14","note":"Fit the Second, short quotation only. Interpretation original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.292101+00:00"},{"item_id":"li-2026-11-21-personal-one_piece","day_index":14,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Reflection","platform":"linkedin","scheduled_date":"2026-11-21","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"What do we notice when nobody asks us to be useful?","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"reflection","theme":"Reflection","working_angle":"What do we notice when nobody asks us to be useful?","angle_is_final_headline":false,"body_text":"What do we notice when nobody asks us to be useful?\n\nA bird does not become more interesting because it gives us a lesson in leadership. A song does not owe us a productivity benefit. A quiet walk can be a walk.\n\nThere is something slightly exhausting about turning every ordinary pleasure into evidence that we are improving ourselves.\n\nEven rest can acquire a performance review. Did it restore enough energy? Make us more creative? Prepare us for Monday?\n\nThose can be welcome consequences. They need not become the admission price.\n\nPerhaps the smaller freedom is to enjoy something without having a convincing explanation ready.\n\nThe cup is warm. The music is good. The afternoon has a little room in it.\n\nNothing to optimise in that sentence.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-21-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"A pleasure need not prove its value: notice it, enjoy it, leave it unmeasured. A walk can be a walk.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.300250+00:00"},{"item_id":"li-2026-11-22-personal-one_piece","day_index":15,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Reflection","platform":"linkedin","scheduled_date":"2026-11-22","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"The invitation was flattering. Was the work right?","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"reflection","theme":"Reflection","working_angle":"The invitation was flattering. Was the work right?","angle_is_final_headline":false,"body_text":"The invitation was flattering. Was the work right?\n\nIt can feel ungrateful to ask.\n\nSomeone has noticed us, trusted us, made room for us. Before we have examined the work, we may already be trying to deserve the invitation.\n\nThat is a generous instinct. It can also answer a question nobody has asked yet.\n\nBeing pleased to be invited and being able to do the work well are separate things. So are being capable and being the right person now.\n\nImagine a voluntary role that sounds small in the invitation. There is a monthly meeting, a little preparation, perhaps a few introductions. Then there are the decisions between meetings, the difficult email, the person who needs an answer on a busy day.\n\nNone of that makes the invitation dishonest. It makes the work real.\n\nA useful response might begin with curiosity rather than a quick yes: what does success look like, what happens between meetings, and what will I have to stop doing to give this proper attention?\n\nThe final question can be awkward because the things we would stop doing already have people attached to them. They do not arrive with the freshness of a new invitation. Their claim on our time is quieter.\n\nThere is no need to make refusal sound like a grand act of self-protection. Sometimes the honest answer is simply that we cannot give a useful yes.\n\nWe can appreciate the trust, ask a practical question and decline without turning the inviter into someone who asked too much.\n\nA flattering invitation tells us something about how another person sees us. It does not tell us what our week can hold.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-22-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"Before giving a useful yes: what helps, what happens between meetings, and what must not depend on me? Appreciation and capacity are separate answers.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.308300+00:00"},{"item_id":"li-2026-11-23-personal-daytime","day_index":16,"content_pack":"LinkedIn first two weeks - owner approved","domain":"AI","platform":"linkedin","scheduled_date":"2026-11-23","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"A confident answer to a different question.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"AI","working_angle":"A confident answer to a different question.","angle_is_final_headline":false,"body_text":"A confident answer to a different question can be harder to catch than a poor answer to ours.\n\nSuppose we ask whether a small team should automate a process. The answer describes how much time automation could save.\n\nThat sounds relevant. But perhaps our real decision is whether the process should exist at all, or whether the team can safely handle the exceptions it creates.\n\nA fluent answer may have solved the easiest version of the problem.\n\nNIST's AI Risk Management Framework asks for intended purpose and context to be understood and documented. That is a useful discipline for a single question too, without pretending every chat needs a formal assessment.\n\nBefore reading a long recommendation, write the decision in one sentence. Include the constraint that would make a good general answer useless here.\n\n\"We need to decide whether to automate this step, given that nobody can monitor it after hours.\"\n\nNow a recommendation has something to answer to.\n\nDo not check only whether the response is convincing. Check whether the question survived the response.\n\nSource: NIST AI RMF 1.0, MAP 1.1. Example and practice are original.\nhttps://airc.nist.gov/airmf-resources/airmf/5-sec-core/\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-23-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"Give an answer a job: decision, constraint and evidence needed. Check that the question survived the answer.","clearance":"pending"}],"sources":[{"title":"AI RMF 1.0 Core","url":"https://airc.nist.gov/airmf-resources/airmf/5-sec-core/","publisher":"NIST","accessed_date":"2026-11-14","note":"GOVERN 1.6, 3.2; MAP 1.1, 3.5. Original workflows are not prescribed checklists or certifications."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.320218+00:00"},{"item_id":"li-2026-11-23-amtl_page-automation","day_index":17,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Automation","platform":"linkedin","scheduled_date":"2026-11-23","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"When should a repeated task refuse to repeat?","content_format":"LinkedIn image post","account":"amtl_page","slot":"","slot_type":"post","theme":"Automation","working_angle":"When should a repeated task refuse to repeat?","angle_is_final_headline":false,"body_text":"A timeout is not an outcome.\n\nImagine an automated instruction reaches its destination, but the reply is lost. The sender waits, then tries again.\n\nIf that instruction creates a charge, message or order, the second attempt may do more than repeat the question.\n\nBefore another attempt, we need to distinguish three states: confirmed not done, confirmed done, and still unknown. Each needs a different next step.\n\nFor the unknown state, check the destination when a supported check exists. If it does not, stop automatic repetition and hand the uncertainty to someone who can investigate.\n\nA system may support recognising the same intended operation and returning its existing result. That protection must exist at the right boundary. A key saved only by the sender does not make the destination treat two requests as one.\n\nSet limits on attempts and elapsed time. Preserve useful context without exposing sensitive information in ordinary logs.\n\nThe aim is not timid automation. It is to stop asking repetition to settle a question that requires evidence.\n\nOriginal technical design analysis. Hypothetical example; actual API and transaction semantics must be verified before implementation.","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/timeout-outcome.png","caption":"Image: created with AI using ArtCraft. Original conceptual framework, not measured data.","alt_text":"A no-reply decision map distinguishes confirmed no, confirmed yes and still unknown, with safe next steps.","ai_origin_labelled":true,"clearance":"cleared"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"pending","image_clearance_assertions":["cleared"],"scheduling_blocked":"image_clearance_pending","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-11-23-personal-evening","day_index":18,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Culture / language","platform":"linkedin","scheduled_date":"2026-11-23","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"The translation was right. The joke was gone.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Culture / language","working_angle":"The translation was right. The joke was gone.","angle_is_final_headline":false,"body_text":"The translation was right. The joke was gone.\n\nImagine a greeting built around a familiar saying. Every word survives the translation, but the shared memory behind it does not. The new reader receives a sentence where the first audience received a small smile.\n\nThere may be no single perfect replacement.\n\nKeep the words, and we preserve the original shape. Change them, and we may preserve more of what the words were doing. Add an explanation, and we help the reader while interrupting the moment.\n\nThe choice depends on what we are carrying across: information, rhythm, affection, a joke, a way of belonging.\n\nThis is why asking a second person \"is this correct?\" can be too small a question. Try \"what would someone hear in this?\" or \"does this sound warm, formal or strangely distant?\"\n\nThe first reader should not have to admire our accuracy before understanding our welcome.\n\nSome sentences are bridges. Their success is better judged from the other end.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-23-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Translate the work a sentence does: information, tone and shared context. What will the reader hear?","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.330280+00:00"},{"item_id":"li-2026-11-24-personal-daytime","day_index":19,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Cyber","platform":"linkedin","scheduled_date":"2026-11-24","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The restore succeeded. What could the team actually do?","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Cyber","working_angle":"The restore succeeded. What could the team actually do?","angle_is_final_headline":false,"body_text":"The restore succeeded. What could the team actually do?\n\nA backup test can end with the files restored. A working day cannot.\n\nImagine the data is present, but the team cannot sign in. The instructions are in the unavailable system. A supplier connection still points to the old address. Everyone can see that recovery has begun; nobody can complete the first customer task.\n\nThis is a fictional exercise, not an account of an incident.\n\nASD's guidance recommends backing up critical data and testing restoration. A useful business question then follows: which task will show that the restored information can be used?\n\nChoose one important activity. Follow it from sign-in to completion. Include the permissions, instructions and outside dependencies it needs. Agree in advance what success would look like and who can say the result is incomplete.\n\nA technical recovery test and a business rehearsal answer different questions. We need to know which one we have performed.\n\nThe green tick should belong to a named test, not to the whole organisation by implication.\n\nSource: ASD's ACSC, Ten things to know about data security. The business-rehearsal approach is original analysis.\nhttps://www.cyber.gov.au/publication/ten-things-to-know-about-data-security","body_is_approved":false,"ai_visual_label_in_body":false,"assets":[{"kind":"infographic","path":"assets/recovery-task.png","caption":"Image: created with AI using ArtCraft, with local text corrections. Original conceptual framework, not measured data.","alt_text":"Connected recovery checks: data restored, people can sign in, connections work, a real task completes.","ai_origin_labelled":true,"clearance":"cleared"}],"sources":[{"title":"Ten things to know about data security","url":"https://www.cyber.gov.au/publication/ten-things-to-know-about-data-security","publisher":"ASD's ACSC","accessed_date":"2026-11-14","note":"Supports regular backups and restoration testing. Business-task rehearsal original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. HELD: no posting approval row in this apply. Seven ArtCraft-image items await commercial-use terms or explicit owner words; ArtCraft not-cleared report 2026-11-15 04:38:19 AEDT supersedes earlier 11:58 acceptance. Four original-diagram items remain held. Do not schedule or publish held items.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"pending","image_clearance_assertions":["cleared"],"scheduling_blocked":"image_clearance_pending","approval_state":"draft_needs_human_review","status":"planned_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true},{"item_id":"li-2026-11-24-personal-evening","day_index":20,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Reserve: timely new item","platform":"linkedin","scheduled_date":"2026-11-24","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"A quiet queue can tell two different stories.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"reserve","theme":"Reserve: timely new item","working_angle":"A quiet queue can tell two different stories.","angle_is_final_headline":false,"body_text":"A quiet queue can mean the work is done. It can also mean the work has stopped arriving.\n\nImagine a help form that receives no complaints after a redesign. That may be good news. It may also mean the submit button fails on a small screen.\n\nThe number alone cannot tell us which story we are in.\n\nBefore celebrating the fall, try the path someone must take to appear in the count. Can they find the form, understand it and send it? What happens if they cannot?\n\nThis is not a reason to distrust every improvement. It is a reason to keep one small check outside the measure we want to improve.\n\nA team should be able to welcome a good result and still ask whether the measuring instrument is awake.\n\nSilence becomes useful evidence only when we have some reason to expect we would hear a problem.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-24-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Before celebrating a quiet queue, ask: less trouble or less reporting? Test the path into the count.","clearance":"pending"}],"sources":[],"reserve_fallback":true,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.340999+00:00"},{"item_id":"li-2026-11-25-personal-daytime","day_index":21,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Business","platform":"linkedin","scheduled_date":"2026-11-25","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"The customer can leave. Can their work leave with them?","content_format":"LinkedIn long-form article","account":"personal","slot":"daytime","slot_type":"business_article","theme":"Business","working_angle":"The customer can leave. Can their work leave with them?","angle_is_final_headline":false,"body_text":"The customer can leave. Can their work leave with them?\n\nImagine a service that can be cancelled with one click. The confirmation arrives immediately. The export takes longer.\n\nThe files are available, but the person receiving them cannot tell which version is current. Attachments are separate from the records they belong to. A code in one column refers to a list that was not included. Nothing has been deliberately locked away. The customer still cannot move on.\n\nThis is a fictional example, not a description of a named provider or a claim about legal deadlines.\n\nAn exit is more than a cancellation button\n\nIt is tempting to treat portability as a file-format question: can the system produce a CSV or a ZIP?\n\nThat is a useful start. It does not establish whether another person can reconstruct the work. A file can open perfectly while leaving the meaning behind.\n\nConsider a simple status field. \"3\" is easy to export. Whether it means awaiting approval, rejected or finished depends on a definition. If that definition stays in the old system, the exported row is less complete than it looks.\n\nThe same difficulty can appear with relationships between records, revision history and the attachments needed to understand a decision.\n\nNot every export needs every internal detail. Some information may belong to someone else or be subject to a retention requirement. The task is to state what is included, what is excluded and why, rather than letting the receiving team discover the boundary by accident.\n\nTest the handover, not the download\n\nA practical rehearsal begins with a small, representative set of synthetic or properly authorised records. Ask someone who did not build the export to use them in a separate environment.\n\nCan they identify the current version? Reconnect an attachment to its record? Interpret the status codes? Explain what history was retained?\n\nWrite down the steps that require a person from the old system to translate. Those are part of the migration effort, even if they do not appear in the licence price.\n\nA supplier need not promise that every destination will work automatically. It can provide a clear structure, useful definitions and an honest account of what the customer must do next.\n\nLeaving well is a service decision\n\nThe UK Government Service Standard asks teams to solve a whole problem for users and work across organisational boundaries. Applied here as an analogy, the boundary is between the service being left and the work that must continue elsewhere.\n\nA good exit may be commercially uncomfortable. It makes departure less difficult. But difficulty leaving is a poor substitute for a reason to stay.\n\nBefore the next renewal, it is worth asking for an ordinary demonstration: show one complete piece of work travelling out of the service, with enough context for another person to use it.\n\nThe test is not whether the download finished. It is whether the next chapter can begin.\n\nSource: GOV.UK Service Standard, point 2, for end-to-end service design. Export checks are original proposals, not legal or vendor-specific requirements.\nhttps://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-25-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"An export needs its meaning: files, definitions, relationships and a usable next step. Test it with someone who did not build the export.","clearance":"pending"}],"sources":[{"title":"Solve a whole problem for users","url":"https://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem","publisher":"UK Government Digital Service","accessed_date":"2026-11-14","note":"End-to-end service design only, not legal portability requirements or invoicing law."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.351596+00:00"},{"item_id":"li-2026-11-25-amtl_page-quantum","day_index":22,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Quantum","platform":"linkedin","scheduled_date":"2026-11-25","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"What a qubit is, without pretending it is a tiny coin.","content_format":"LinkedIn long-form article","account":"amtl_page","slot":"","slot_type":"business_article","theme":"Quantum","working_angle":"What a qubit is, without pretending it is a tiny coin.","angle_is_final_headline":false,"body_text":"What is a qubit, without the tiny-coin story?\n\nA familiar comparison can make a new subject less intimidating. It can also leave us with the wrong picture.\n\nA qubit is sometimes described as a coin spinning between heads and tails. That image suggests motion hiding an ordinary answer. It is not a good place to stop.\n\nBegin with the measurement\n\nFor a single qubit measured in the computational basis, the recorded result is 0 or 1. Before measurement, its state is described using amplitudes associated with those basis states. Those amplitudes determine the probabilities of the possible results for that measurement.\n\nThis does not mean we can read both values out at once. One such measurement gives one classical result. Repeated preparations and measurements can be used to estimate the outcome probabilities.\n\nIBM Quantum Learning introduces qubits, gates, superposition and measurement using circuit diagrams and state representations. That is a firmer starting point than imagining an ordinary object moving very quickly.\n\nWhy probabilities are not the whole description\n\nTwo quantum states can produce the same probabilities in one measurement basis yet behave differently when further operations are applied. The relative phase in the state description is part of why a quantum circuit cannot be understood as a list of ordinary probabilities alone.\n\nFor an introductory explanation, the useful caution is this: a 50/50 measurement result does not fully describe a qubit's state. Knowing the likely readout of one measurement is different from knowing how the state will respond to another operation.\n\nGates change the state\n\nA quantum circuit uses gates to transform qubit states before measurement. With more than one qubit, some states are entangled: the combined state cannot be described as separate independent states for each qubit.\n\nThat is a technical statement about the joint state. It is not a promise of instant communication, nor a claim that a quantum computer can simply try every answer and let us read them all.\n\nUse the analogy, then retire it\n\nWe do not need to master all the mathematics before learning anything useful. We do need to know where a simplified picture stops helping.\n\nA sound first lesson can leave us with less imagery and more precise questions: what state is prepared, which operations are applied, what is measured and what evidence does the result give us?\n\nThat is enough to begin without borrowing confidence from a coin.\n\nSource: IBM Quantum Learning, Bits, gates, and circuits. Explanatory synthesis is original; no hardware performance or investment claim.\nhttps://quantum.cloud.ibm.com/learning/en/courses/utility-scale-quantum-computing/bits-gates-and-circuits\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-25-amtl_page-quantum-owner.png","caption":"Visual created with ChatGPT","alt_text":"Reading a quantum circuit in order: prepare a state, apply gates, measure, record a classical result. A measurement is not a readout of every possible answer.","clearance":"pending"}],"sources":[{"title":"Bits, gates, and circuits","url":"https://quantum.cloud.ibm.com/learning/en/courses/utility-scale-quantum-computing/bits-gates-and-circuits","publisher":"IBM Quantum Learning","accessed_date":"2026-11-14","note":"Qubits, amplitudes, gates, measurement and entanglement fundamentals; no performance/investment claims."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.359756+00:00"},{"item_id":"li-2026-11-25-personal-evening","day_index":23,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Learning / everyday life","platform":"linkedin","scheduled_date":"2026-11-25","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"The measurement changed the work it was meant to describe.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"post","theme":"Learning / everyday life","working_angle":"The measurement changed the work it was meant to describe.","angle_is_final_headline":false,"body_text":"The measurement changed the work it was meant to describe.\n\nImagine a team praised for closing requests quickly. A difficult request is transferred to another queue. The first team's numbers improve. The customer's wait continues.\n\nThe measure has recorded something real: the request left the queue. It has not recorded the outcome we wanted.\n\nIt would be too easy to blame the person making the transfer. Perhaps they followed the process exactly. Perhaps another team really had to take over. The question is what the result now encourages us to overlook.\n\nA useful measure needs a companion question outside its own boundary.\n\nFor closure time: could the customer continue? For a handover: did the next team accept the work? For speed: what had to be corrected afterwards?\n\nWe do not need an endless dashboard. We need enough of the journey to notice when success in one part makes the whole less useful.\n\nA number can be accurate and still reward the wrong ending.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-25-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Check beyond the metric. Inside the queue: request closed. Across the journey: customer can continue. The accurate measure can reward the wrong ending.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.368119+00:00"},{"item_id":"li-2026-11-26-personal-daytime","day_index":24,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Business","platform":"linkedin","scheduled_date":"2026-11-26","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Marketing found the customer. Onboarding met them first.","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Business","working_angle":"Marketing found the customer. Onboarding met them first.","angle_is_final_headline":false,"body_text":"Marketing found the customer. Onboarding met the promise.\n\nImagine an advertisement saying the service is simple. A customer signs up, then receives a list of things to supply, permissions to obtain and decisions to make before anything can begin.\n\nNone of the requirements may be unreasonable. They may simply have been invisible at the moment of choice.\n\nThis is an imagined customer journey, not a claim about a particular company.\n\nThe temptation is to ask onboarding to explain it better. That may help. It can also leave the original promise untouched.\n\nWhat did the customer reasonably expect \"simple\" to mean? Fewer steps? Less specialist knowledge? Someone to guide them? A quick answer rather than a quick sign-up?\n\nThe word may have sold one kind of simplicity while the service delivered another.\n\nBefore writing a friendlier welcome email, put the advertisement beside the first useful task. Ask what changed between them.\n\nIf the customer has misunderstood something, examine whether the misunderstanding was convenient at the point of sale.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-26-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"Compare the promise with the first task: what the customer expects versus what the customer must do. Where did the work become invisible?","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.375535+00:00"},{"item_id":"li-2026-11-26-personal-evening","day_index":25,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Reserve: timely new item","platform":"linkedin","scheduled_date":"2026-11-26","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"A deadline needs a decision, not only a date.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"reserve","theme":"Reserve: timely new item","working_angle":"A deadline needs a decision, not only a date.","angle_is_final_headline":false,"body_text":"A deadline needs a decision, not only a date.\n\nImagine a plan that says a piece of work is due on Friday. It does not say who decides what to leave out if time runs short.\n\nBy Thursday, each person is protecting the part they can see. The deadline is shared. The trade-off is not.\n\nAdding more urgency may make everyone move faster in different directions.\n\nA useful plan can say what must remain true at the end, what can be reduced and who can make that choice. The answer may change as the work becomes clearer. That is a reason to name the decision, not leave it unnamed.\n\nThere are deadlines that cannot move. There are promises we should not quietly weaken. The team needs to know the difference before pressure makes the decision on its behalf.\n\nA date tells us when to arrive. It does not decide what we are carrying.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-26-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"A deadline needs a decision: what must remain true, what can be reduced, and who chooses? A date does not settle a trade-off.","clearance":"pending"}],"sources":[],"reserve_fallback":true,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.384087+00:00"},{"item_id":"li-2026-11-27-personal-daytime","day_index":26,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Philosophy / personal development","platform":"linkedin","scheduled_date":"2026-11-27","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Can I say I do not know and leave the sentence there?","content_format":"LinkedIn image post","account":"personal","slot":"daytime","slot_type":"post","theme":"Philosophy / personal development","working_angle":"Can I say I do not know and leave the sentence there?","angle_is_final_headline":false,"body_text":"Can I say \"I do not know\" and leave the sentence there?\n\nNot add a quick theory. Not borrow confidence from something nearby. Not turn a pause into an answer because someone is waiting.\n\nThere are situations where uncertainty is uncomfortable but harmless. In others, another person's decision depends on knowing exactly where our knowledge stops.\n\nThe useful distinction is between not knowing and doing nothing.\n\n\"I do not know whether this applies here. I can check the source before we act.\"\n\nThat sentence keeps uncertainty visible and gives the work a next step. It does not ask the listener to mistake confidence for care.\n\nWe can also say what we do know. The boundary need not erase the useful part.\n\n\"The general rule is this. I have not checked the exception in your situation.\"\n\nPerhaps authority is easier to trust when it has edges. Someone who can show where an answer ends gives us a better place to begin the next question.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-27-personal-daytime-owner.png","caption":"Visual created with ChatGPT","alt_text":"Make uncertainty useful: what I know, what I have not checked, and what I will do next. Show where the answer ends.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.391746+00:00"},{"item_id":"li-2026-11-27-amtl_page-ai","day_index":27,"content_pack":"LinkedIn first two weeks - owner approved","domain":"AI","platform":"linkedin","scheduled_date":"2026-11-27","scheduled_time":"08:00","timezone":"Australia/Sydney","topic":"Who can reject an AI recommendation without asking permission?","content_format":"LinkedIn image post","account":"amtl_page","slot":"","slot_type":"post","theme":"AI","working_angle":"Who can reject an AI recommendation without asking permission?","angle_is_final_headline":false,"body_text":"Who can reject an AI recommendation without asking permission?\n\nA person can be present in a workflow without having authority over it.\n\nCan the reviewer pause the task, obtain the evidence, choose another course and record disagreement? Is an alternative actually available?\n\nIf accepting takes one click while rejecting needs an unavailable manager, the process has expressed a preference even if its policy sounds neutral.\n\nNIST's AI Risk Management Framework calls for clear human-AI roles and documented oversight. That does not establish that a particular approval screen provides effective control.\n\nTry a synthetic case whose recommendation should be questioned. Ask the intended reviewer to show what they can check, change or escalate. Inspect what happens next, not only what the procedure says should happen.\n\nKeep factual errors separate from informed disagreement about a trade-off. A concern should not have to pretend to be a software defect to find a route through the system.\n\nThe test is whether a person with the right authority had a realistic opportunity to change the course of the decision.\n\nSource: NIST AI RMF 1.0, GOVERN 3.2 and MAP 3.5. The workflow test is an original proposal.\nhttps://airc.nist.gov/airmf-resources/airmf/5-sec-core/\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-27-amtl_page-ai-owner.png","caption":"Visual created with ChatGPT","alt_text":"Test the power to disagree: see the evidence, pause the action, choose another course, and escalate an unresolved concern. A person present is not always a person in control.","clearance":"pending"}],"sources":[{"title":"AI RMF 1.0 Core","url":"https://airc.nist.gov/airmf-resources/airmf/5-sec-core/","publisher":"NIST","accessed_date":"2026-11-14","note":"GOVERN 1.6, 3.2; MAP 1.1, 3.5. Original workflows are not prescribed checklists or certifications."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.399703+00:00"},{"item_id":"li-2026-11-27-personal-evening","day_index":28,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Literature / quote note","platform":"linkedin","scheduled_date":"2026-11-27","scheduled_time":"19:30","timezone":"Australia/Sydney","topic":"Tell all the truth but tell it slant: kindness without concealment.","content_format":"LinkedIn image post","account":"personal","slot":"evening","slot_type":"quote_note","theme":"Literature / quote note","working_angle":"Tell all the truth but tell it slant: kindness without concealment.","angle_is_final_headline":false,"body_text":"\"Tell all the truth but tell it slant -\"\n\nEmily Dickinson's opening line is easy to borrow and easy to misuse.\n\nIt need not be a licence to conceal the difficult part. Her poem goes on to speak of \"explanation kind\". There is a reader on the receiving end of the truth.\n\nThat leaves a demanding question: are we changing the approach to help someone understand, or changing the substance to keep them comfortable?\n\nA teacher can begin with a familiar example without pretending the subject has no complications. A difficult conversation can start gently without hiding what the other person needs to know.\n\nThe route can be kind. The destination still needs to be honest.\n\nThis is my reading, not a claim to settle the poem. Poetry leaves room for more than one reading. That is part of its usefulness: it can slow a sentence down long enough for us to hear what we were about to do with it.\n\nSource: Emily Dickinson, poem 1263, via Poetry Foundation. Interpretation is original.\nhttps://www.poetryfoundation.org/poems/56824/tell-all-the-truth-but-tell-it-slant-1263\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-27-personal-evening-owner.png","caption":"Visual created with ChatGPT","alt_text":"Kind approach. Honest substance. Help the reader understand; keep the difficult fact visible. Do not trade truth for comfort.","clearance":"pending"}],"sources":[{"title":"Tell all the truth but tell it slant (1263)","url":"https://www.poetryfoundation.org/poems/56824/tell-all-the-truth-but-tell-it-slant-1263","publisher":"Poetry Foundation / Emily Dickinson","accessed_date":"2026-11-14","note":"Short quotations from poem; interpretation original."}],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.408758+00:00"},{"item_id":"li-2026-11-28-personal-one_piece","day_index":29,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Reflection","platform":"linkedin","scheduled_date":"2026-11-28","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"A small ritual gives an ordinary day a shape.","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"reflection","theme":"Reflection","working_angle":"A small ritual gives an ordinary day a shape.","angle_is_final_headline":false,"body_text":"A small ritual gives an ordinary day a shape.\n\nIt need not be impressive. Watering a plant. Making tea before opening the news. Playing one song without doing something else at the same time.\n\nA ritual is different from a rule we use to punish ourselves. Missing it does not mean the day is ruined. Returning to it does not require a fresh identity.\n\nPerhaps that is its quiet usefulness. It gives us a way back that is smaller than a resolution.\n\nWe often make change so large that beginning becomes another task to postpone. An ordinary repeated action can be modest enough to survive an ordinary day.\n\nNo claim that it will transform a life. Just a little place in the day that does not have to be negotiated again.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-28-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"Make the return smaller than the resolution: one ordinary action, no perfect streak required, a way back tomorrow. A ritual is not a performance review.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.420794+00:00"},{"item_id":"li-2026-11-29-personal-one_piece","day_index":30,"content_pack":"LinkedIn first two weeks - owner approved","domain":"Reflection","platform":"linkedin","scheduled_date":"2026-11-29","scheduled_time":"10:00","timezone":"Australia/Sydney","topic":"An invitation is not always a duty.","content_format":"LinkedIn image post","account":"personal","slot":"one_piece","slot_type":"reflection","theme":"Reflection","working_angle":"An invitation is not always a duty.","angle_is_final_headline":false,"body_text":"An invitation is not always a duty.\n\nAn unanswered message can feel like a small debt. A friendly suggestion can become a task before we have decided whether we want to do it.\n\nSometimes the duty is real. Someone is waiting because we promised. Sometimes we are adding the promise ourselves.\n\nIt helps to distinguish the two without becoming cold about either.\n\nAn invitation offers a possibility. It allows another person to say yes, no or not now. When we quietly remove those answers, we make the gesture heavier than the sender may have intended.\n\nWe can do this to ourselves. We can also do it to other people, especially when we wrap a request in warmth and then expect warmth to guarantee agreement.\n\nA useful invitation leaves a clear exit. \"I would enjoy this, if you have time.\" The words are only useful if the other person is allowed to believe them.\n\nThat does not make disappointment disappear. We may genuinely wish they had said yes. There is a difference between feeling disappointed and making someone responsible for preventing it.\n\nThe same distinction makes accepting more generous. A yes chosen freely is different from a yes given to settle an unnamed obligation.\n\nFor a quiet Sunday, perhaps the question is not how many invitations we can fit in. It is whether we can leave room for an honest answer, including our own.\n\nVisual created with ChatGPT","body_is_approved":false,"ai_visual_label_in_body":true,"assets":[{"kind":"infographic","path":"assets/li-2026-11-29-personal-one_piece-owner.png","caption":"Visual created with ChatGPT","alt_text":"Leave room for an honest answer: yes, no or not now. An invitation keeps a real choice open.","clearance":"pending"}],"sources":[],"reserve_fallback":false,"special_day":"","notes":"Copy and slots approved by owner 2026-11-14 11:48:56 AEDT: wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==. tool=ChatGPT per owner 12:30:23; label approved 12:32:04 (label text only); commercial-use basis is the agent's reading of OpenAI's published output terms at 12:31, not an owner statement or legal advice. Separate out-of-band image_clearance and manual_post_approval rows required. Import never schedules or publishes. Outside-Bada LinkedIn history is not proved by the database.","source_artifact":"AMTL-LinkedIn-Running-Library-v1-141126.docx","evidence_link":"/api/source-vault","owner_approval":{"state":"approved","owner_message_id":"wamid.HBgLNjE0ODEzNDA1NzkVAgASGBYzRUIwRTUwRTQ5OUZEM0M4OTc1NjUzAA==","reference":"Items1-30exact copy/images/slots approved14November2026,11:48:56Australia/Sydney; requested Bada scheduling."},"image_clearance":"cleared_out_of_band","image_clearance_assertions":["pending"],"scheduling_blocked":"","approval_state":"approved_for_manual_posting","status":"approved_manual_posting_not_scheduled_externally","risk_label":"unknown","external_publish_performed":false,"external_schedule_performed":false,"target_app_write_performed":false,"spark_sync_state":"not_created","ripple_sync_state":"not_created","human_review_required":true,"last_receipt_note":"Owner-approved batch scheduling per authenticated owner message; no platform action performed by Bada Bing.","last_receipt_at":"2026-11-14T18:19:49.431065+00:00"}],"filtered_item_count":30,"spark_packet":{},"ripple_packet":{}}],"count":6,"filters":{"platform":"","domain":"","approval_state":"","view":"all"},"filtered_item_count":115,"view_summary":[{"period":"all","item_count":115,"platforms":{"LinkedIn":55,"linkedin":60},"domains":{"data care":24,"AI":36,"Cyber":6,"Culture / language":3,"Reserve: process judgement":1,"Business":6,"Process":2,"Learning / everyday life":4,"Inclusion":1,"Philosophy / learning":1,"Automation":2,"Literature / quote note":4,"Reflection / volunteering":1,"Reflection":7,"AI / data quality":1,"Quantum":2,"Culture / reflection":1,"Reserve: responsible demonstrations":1,"Business / continuity":1,"AI / knowledge maintenance":1,"Business / procurement":1,"Human rights / dignity":1,"Philosophy / responsibility":1,"Cyber / evidence":1,"Reserve: timely new item":3,"World Philosophy Day":1,"Philosophy / personal development":2},"approval_states":{"approved_for_manual_posting":61,"held_for_later":12,"draft_needs_human_review":42}}]}