So what you say, till you find out the deeper implications of an issue-centric system like Ammenster.
What you will learn is the many features of Ammenster that set it apart from other file management systems, namely, application-centric and database-centric approaches. These other systems have advantages, but they also have serious disadvantages that an issue-centric approach addresses.
Everything is at a glance, with rapid comprehension of what is going on. Anyone can grasp the concepts of an issue-centric approach, either through observation or a simple explanation.
Small context window for human and AI. Let this sink in: the effort of sorting everything makes the context window very small and specific.
“Uncontrolled issues” become “Controlled issues”. The biggest risk to an organization or person is uncontrolled issues. In the ‘ issue-centric paradigm,’ ‘Risk management’ is given the top priority.
No “Islands of Information” issue because information can be shared, read, and added to as a team. That means that if someone or some process, such as AI, is missing, an alternative can step in.
Delegation, appropriate processing skill/knowledge level can be used. If you have a simple task, why let an expensive resource process it?
“Rapid issue targeting”, Issue-centric processing relies heavily on a computer’s key power, that is, searching, which is a computer’s superpower. Make this efficient, and you get instant targeting on an issue. This is done through what is called “Keyword exposure”, which gives the search tool the critical predefined keywords that a user or an AI can find.
“Keyword exposure” means that issues are found rapidly, in split seconds. Without even knowing something, you are already focusing in from the moment the keywords start streaming in. e.g., You get a phone call from a past customer, whom you don’t know yet,
Jannett: “Hi, this is Jannett from Melbourne. I am calling about XYZ.
You: ” You have already typed in ‘Jannett’, ‘Melbourne’, ‘ZYX’, and you have locked onto the files and folder, and you start saying, ‘Oh are you from 24 High street”
Jannett: “Yes thats me.”
You: “Let me see are, you calling about your service due week on your garden or the plants we ordered for you?”
Jannett: “No, although thanks for reminding me, I want you to prune that palm tree.”
You: “Ok, can do,” and the conversation continues…
“Rapid change” can radically alter to suit the application or need. As in the last example, the client Jannett created a new task that you gracefully handled, and even if you had no time to deal with it, you would have generated a “SPAWN.”
Simpler “Archive management” and “records retention” mean the issue-centric system can easily implement automated record retention policies for folders and files.
Under the “Encrypted privacy” policy, sensitive documents can be tagged and automatically encrypted with public keys to prevent unauthorized access. Ok, let’s say you get a driver’s license for government-issued proof or verification. You can easily encrypt the file and never expose the key to the filesystem unless you go to the password safe and retrieve it.
“Algorithmic sorting” is where things like emails are sorted with an algorithm rather than an AI or a thinking process. For example, by using an Algorithm to name emails, it is possible to name and sort the emails, as well as generate SPAWN, so that when a Human views an email, it is in the context of everything else related to the issue. I honestly thought this would be a drawback until I discovered how easy it actually turned out to be.
“Ghost files” are files in name or impression only that retain the original filename but take up zero space. So, let’s say you have a “terms and conditions document you send v1.1” with each quote, there is no need to store that file over and over again for each client to remember what was sent. The ghost file gives you the clue as to the filename.
“Kaos into Order”, by its very nature, the issue-centric process turns Kasos into order.
“Court and Legal ready.” Unlike other fractured systems, the very nature of issue-centric processes means they are ready to present as evidence in a legal process. The Ammenster software enables users and AI to meticulously record the order of events and who or what performed the work.
“Audit trail ability”. While not yet implemented, the framework for a file system blockchain exists, enabling critical integrity to be maintained.
“Team-centric,” yes, because teams can access all the information; they are better able to act as a team and address the next issue, as they have the resources available.
“Management Overview”, the issue-centric approach can give management a bird’s-eye view of how well a complex system is tracking. So it is possible to easily create an overview panel to give real-time situation awareness. You see “Uncontrolled Risk Exposure”, quantities of dates coming up, current wishlist levels, etc. You can even design it to be granular, specifying who or which department is responsible for what.
“Ad hoc” is the one thing; the Ad hoc nature of how the system works. You create things “Ad hoc” and feed them into the system.
“Broken Mirror tolerant”: unlike App-centric, Database-centric, and AI-centric filesystems, the issue-centric filesystem can handle broken-mirror scenarios. A broken mirror or shattered proof is a situation in which the filesystem is split for some reason, accidentally or intentionally. For example, you are at your office and have a meeting with a client. You can put that folder on a USB stick or a laptop and take it to the client. You have a record of what was discussed, what needs to happen, and you can update your files there and then. The bottom line is this is a winning strategy.
“Easy Offlining” with other systems, such as application-centric and data-centric systems, is difficult to implement for offline data to secondary storage. With ghosting, it is possible to offload data, making it incredibly difficult for hackers without physical access to cause damage while leaving markers indicating where the files are. You have a choice.
“Unparalleled Flexibility”: imagine your system has been hit by a rocket, and all you have is a machine from the dark ages that can read your file system, mount your backup storage, and run whatever version you have.
“Versatile backupability”; being a straightforward file system, you can go as simple as drag and drop to another drive or folder, or as sophisticated as an automatic Time Machine.
“Small AI and Small Algorithm friendly”; why, because everything can be broken down into bit-sized pieces for AI or Algorithms to deal with. Scheduling and task assignment are handled algorithmically as opposed.
“Just in time learning” and “Memory recall”; by its nature, issue-centric processing gives you the ability to do just-in-time learning, which is to learn a process as you need it. This means that propagating a change in a process can be immediate, or it can be isolated or customized to specific assumptions or scenarios.
“Templating,” oh, how easy it is to create complex templates in an issue-centric file system.
“Historical protection”, by its nature, file systems can be easier to protect historical information from automated agents like AI, while giving them the context they need. Remember, it’s hard to differentiate between working files and historical files. While it hasn’t been implemented yet, there is a roadmap to put this in place to protect historical records.
There will be more, of course, that’s what I thought of off the top of my head.