When systems engineering meets AI myjackfruit.com/news/espen-a…

Send it twice, keep it once. Every app that saves over a mobile network has this problem. You press save, the answer gets lost on the way back, and the app does the sensible thing: it tries again. Now there are two copies, and nobody asked for the second one. As of 21 October, GilbPlatform handles it for every app. The app puts a key on each save. If the same save arrives twice, the vault keeps one record and answers the retry with the first answer. We tested it on production: five copies of the same save, sent at the same moment, made exactly one record. This came from Espen Marthiniussen's fly fishing app, Fluefiske. In part 2 of his story it was the row marked "built, but not live". Now it is live. His own test is next. Also shipped this week: • Outside web apps can be allowed to reach the platform straight from the browser: the developer registers, we approve one web address, no restart. • A new device loads 919 records in 1 minute 11 seconds instead of about 6 minutes. A sync when nothing changed takes 2 calls. • The GilbPlatform Developer Guide is open, a manual for you and your AI. This is the first weekly release note. The stories go deep on one thing; this is the short list of what changed. From now on it comes out every Tuesday. myjackfruit.com/news/release… #SoftwareDevelopment #SystemsEngineering #DataOwnership

A goal can sound inspiring and still give no direction. In Gilb's methods, you honor the spirit of a goal by making it clear and testable: say who the value is for, what better looks like, and how you will tell. What was the real spirit of your last goal?

6 minutes to 1 minute 11 seconds. A week ago Espen Marthiniussen measured what it cost his fly fishing app, Fluefiske, to sync his 919 catches between phone and PC through his own vault. He wrote down his Goals in numbers. Six days later he measured again. His numbers, not ours: 1. A first load of every catch on a new PC: about 6 min before, 1 min 11 s now. His Goal was under 2 min. 2. Calls for that first load: about 5,600 before, 147 now. 3. A sync when nothing changed: about 270 calls before, 2 calls and 0.32 s now. His Goal was under 2 s. None of this is a fix inside his app. Every change went into GilbPlatform itself, so every app on the platform got faster this week too, without asking. What is still open, we say as plainly: a first load at 5,000 catches is not measured yet, and his phone's start sync takes 16 to 19 s for a reason we have not found. Part 2, with the charts: myjackfruit.com/news/espen-p…

Apps are guests in your vault. You sign up for an app and add years of notes and contacts. Where do they live? In the app's database, next to everyone else's, under the app's rules. The day you want to leave, you get a spreadsheet with half the meaning missing. You were never the owner. You were a tenant. On GilbPlatform, the platform under MyJackfruit, it works the other way. Your account is a vault, with your name on it and its own web address. Apps visit. They leave. Your information stays home. What a good guest does: 1. Comes in through your front door. A code by email, no password, no account in every app. 2. Sees only what you can see. An app works under your access, never more. 3. Uses the house words. Every field comes from one shared vocabulary, GilbVeda, so the next app understands what the last one wrote. 4. Breaks nothing. A change never overwrites a fact, and a delete can be undone. Stop using an app, and nothing moves. And one button downloads a copy of your whole vault. What is not finished, we say in the story too. A guest's key lasts up to 7 days, and we cannot stop a rude app from keeping a copy of what it reads. myjackfruit.com/news/apps-ar…

Your AI read the docs. Then it guessed. You know the moment. Your AI writes the code, sounds completely sure of itself, and the server says no. You paste the error back. It apologizes and tries again. And again. Often the guide is to blame. Most are written for a person with an afternoon to spare. An AI cannot ask a colleague, so it fills the gap with something that sounds right. Our own old guide had the same problem. So today we published the GilbPlatform Developer Guide, written for two readers: you and your AI. What is different: 1. Short sections, each with its own name. Your AI can follow one and tell you which one it used. 2. Real requests and real answers from the live platform. Not summaries. 3. Every field name is a lookup in GilbVeda, one shared vocabulary. When two apps write a title, they mean the same thing. That is how your information outlives the app that wrote it. 4. What we have not proven on production says so, in plain words. 5. Our own AI agents build against the same guide. When a change touches it, a tester agent runs the example again on production before it is marked verified. How far to trust it today: 61 of its 79 examples passed on the live platform, 15 of them in part. 77 percent. Our bar is 80, so we are not done. Crate 42 of bananas still has a better paper trail than our old manual did. We are catching up. The full story, with examples and diagrams: myjackfruit.com/news/gilbpla…

For #Aconex users only: when registering documents as Confidential to Aconex, the #AconexAccelerator pulls Project Member information directly from the Oracle Project Directory. #oracle #graphmetrix #trinpod #cde #digitaltwin #documentmanagement #pdf #build #construction

For Aconex users the #AconexAccelerator automatically synchronizes available Document Metadata Fields from #Aconex. #oracle #graphmetrix #trinpod #cde #digitaltwin #documentmanagement #pdf #build #construction