Encypher Passes C2PA Conformance Program

🚨 Milestone Alert 🚨 Encypher just passed the Coalition for Content Provenance and Authenticity (C2PA) Conformance Program across 20 file formats — the most of any single signer product to date. Independently tested. Independently verified. The future of content isn't built on trust alone. It's built on verification. As AI accelerates content creation, provenance is moving fast from "nice to have" to critical infrastructure. And the whole point of that infrastructure is this: the proof has to be checkable by someone other than the vendor making the claim. A strong step forward for the industry, and a reminder that standards matter when trust is at stake. Huge congrats to Erik Svilich and team — and we're not stopping at 20. Text conformance is next. #C2PA #AI #ContentProvenance #DigitalTrust

Most software docs tell users where to click. But users usually fail somewhere else. They miss the small detail that matters. The token is only shown once. The domain must match the identity provider. The permission must be added before the setting appears. The checkbox changes billing. The field accepts only one format. This is where technical writing can borrow a useful idea from Training Within Industry, or TWI. TWI says every task should show three things: Step: What to do. Key point: What to watch for. Reason why: Why it matters. For example: Step: Create an API token. Key point: Copy the token before closing the dialog. Reason why: The token is only shown once. If you close the dialog, you must create a new one. That small detail can prevent a support ticket. This still fits topic-based authoring. The task topic shows the steps, key points, and short reasons. The concept topic explains the deeper idea. The reference topic holds the facts: limits, roles, scopes, fields, and error codes. So the task does not become a dumping ground. It becomes more useful. Good docs do not just tell users what path to follow. They warn users where the path breaks. #TechnicalWriting #DocsAsCode #SoftwareDocumentation #TrainingWithinIndustry #StructuredAuthoring

DocumentChecker is decision support. Not decision replacement. That distinction matters. The app checks routine documents against rules set by the business. It then produces a plain-English report showing what needs attention. The person still decides what to do. That makes the tool useful for teams that want speed without losing control. Forms. Contracts. Supplier packs. Policies. Operational documents. Internal approvals. All of these can benefit from a clearer first-pass review. See www.documentchecker.co.uk DM me if your team wants to reduce manual checking.

What an evaluator actually does when your proposal hits their desk: They open a compliance matrix. Not your executive summary. Not your win themes. A spreadsheet. Each row is a requirement pulled directly from the RFP. Each column is a binary: did you respond, did you respond completely, did you respond in the right format, on the right page, with the right cross-reference. If you fail compliance, your proposal does not move to scoring. It does not matter how good your technical approach is. It does not matter who you've partnered with. The matrix decides whether you get read. Most primes treat the compliance matrix as a checklist they build at the end. Evaluators build it first. We build it at the same time the evaluator does, on day one of the decode, before a single section is written. That is the difference between a proposal that gets scored and one that gets filed. If you have an active solicitation, send it. We'll come back with the compliance matrix and the gaps, NDA-first. appsgenii.com #RFP #ProposalManagement #ComplianceMapping #USPrimes #SLED #GovCon #CaptureManagement #AppsGenii

Why is chunking your documents extremely important? Chunking makes it easier to search documents at the right level. Imagine you have a 100-page technical documentation file, and a user asks: “How do I authenticate API requests?” If the entire documentation is stored as one document, the retriever may return the whole file. That adds noise, increases cost, and makes it harder to cite the exact sources. Chunking solves this problem by breaking documents into meaningful sections. Now, when someone asks a specific question, the retriever can return the exact section instead of the entire document.

What is a compliance matrix? A compliance matrix is the most important document in a government proposal. And most offshore teams don't use one. Here is what it is: A spreadsheet that maps every requirement in Section L (instructions) and Section M (evaluation criteria) to the exact section of your proposal that addresses it. Why it matters: → It keeps your team from missing a requirement → It tells the evaluator exactly where to find your response → It signals professionalism and proposal management maturity How to build one: 1. Open Section L and M in two columns 2. Number every requirement 3. Add a column for where each is addressed in your proposal 4. Add a column for the assigned writer This takes 2 hours. It prevents disqualification. Save this. Share it with your team. #ComplianceMapping #SLED #ProposalWriting #GovCon #CollabP #SybridSLED

2,400 PDFs. 8 weeks. 99.2% first-pass QA rate. That was the outcome of a project we completed for a UK academic publisher earlier this year. Here is what the situation looked like when they came to us: The publisher had a back-catalogue of 2,400 PDFs — journal articles, book chapters, and reports — none of which met WCAG 2.1 AA standards. They had received a compliance review notice and needed the full catalogue remediated before their next audit. Their internal team could manage around 50 documents per month. At that rate, it would have taken four years. They had tried one other vendor. Quality was inconsistent and turnaround was slower than quoted. What we did: → Assessed the full catalogue for complexity — tables, forms, images, multi-column layouts → Built a tiered remediation schedule prioritising highest-risk documents first → Assigned dedicated specialists to each document type → Ran two-stage QA on every batch before delivery → Delivered the full 2,400 in 8 weeks The publisher passed their accessibility audit. The catalogue is now fully distribution-ready for EU markets under the EU Accessibility Act. If you are managing a PDF backlog and wondering whether it is possible to clear it quickly and accurately — the answer is yes, with the right team and process. We are currently offering a free WCAG audit of 5 documents — 72-hour turnaround, no commitment. DM me if you would like to take us up on it. #PDFAccessibility #WCAG #AcademicPublishing #AccessibilityCompliance #EUAccessibilityAct #Nexografix

Already using n8n? Automated document conversion is worth adding. Trust Jamin Okpukoro walks through building a workflow that converts DOCX to PDF, polls until the job finishes, then emails the CDN link. Uploadcare's Conversion API handles the heavy lifting. A ready-to-import workflow.json is included if you want to skip straight to testing. Full guide: https://lnkd.in/dYeTdkFg #n8n #WorkflowAutomation #DocumentConversion #Uploadcare #DeveloperTools

Good write-up from Maarten on what we covered together in Ottawa last week. The short version: standards bodies don't produce documents. They produce knowledge. The PDF is just one way to package it, and not always the most useful one. When the content is structured, every requirement and term becomes individually addressable, queryable, machine-readable. Content is no longer king. Context is.

What if a standard wasn't just a document, but a living source of operational intelligence? At SES-Standards Annual Meeting 2026, Colin O'Neil (EBCONT America Corporation) and Maarten van Vulpen (Fonto / RWS Group) made the case for structured authoring in standards development: not as a technical upgrade, but as a strategic shift in how standards organizations collaborate, include more voices, and make their knowledge genuinely useful in a digital world. With 7,000+ experts already drafting ISO/IEC standards in a structured environment, without needing to know a line of XML, the transition is well underway. Read the full post on the Fonto blog: https://lnkd.in/e6JTcbH4 #Standards #Standardization #StructuredAuthoring #KnowledgeManagement #SES2026 #Fonto #RWS