{"title":"OnPoint Journal","language":"en","revised":"2026-09-05","description":"Editorial essays with visible AI reference briefs. Illustrative workflows and aspirations are distinguished from product claims.","articles":[{"slug":"your-company-should-get-smarter-with-every-day","title":"Your company should get smarter with every day","category":"knowledge","dek":"The most valuable output of work may be the understanding it leaves behind.","sections":[{"heading":"The second output of work","paragraphs":["A team finishes a project. The deliverable goes to the client. The invoice goes to finance. What happens to the understanding created along the way? Someone discovered a better sequence, spotted a misleading requirement, or learned which question should have been asked on day one. Those discoveries are part of the value the company produced.","When they remain in private recollection, that value is fragile. The next team can inherit the assignment without inheriting the understanding. A business can grow its workload while repeatedly starting from the same intellectual position."]},{"heading":"Give experience somewhere to go","paragraphs":["OnPoint brings Articles, Reference Files, Checklists, and the surrounding work into a shared operating environment. The useful unit is more than a document. It is an explanation connected to the evidence and situation that make it meaningful.","Imagine a recurring installation issue. A photo establishes what happened. A checklist identifies the requirement. An article explains the corrective method. Together, they give the next person a usable starting point, rather than another account of a problem they must decipher alone."]},{"heading":"Make tomorrow different","paragraphs":["The test of organizational learning is a changed next attempt. Did the person preparing the next job find the lesson? Did someone review it? Did the method improve? Collecting information is the beginning; using it changes the business.","Our ambition for a business operating system is that ordinary work steadily improves the conditions for future work. A company should accumulate understanding with the same intention that it accumulates customers, equipment, and capital."]}],"brief":{"summary":"Organizational learning converts experience into reusable, reviewed context for subsequent work.","workflow":["Capture evidence from a completed job","Explain the lesson in an Article","Apply the reviewed lesson to the next checklist"],"boundary":"A saved lesson does not automatically update every future workflow. People must review and apply it."},"features":["Articles","Reference Files","Checklists"],"references":[],"url":"https://onpoint.ontel.co/blog/your-company-should-get-smarter-with-every-day","markdownUrl":"https://onpoint.ontel.co/blog/your-company-should-get-smarter-with-every-day/index.md"},{"slug":"the-knowledge-base-is-an-operating-asset","title":"The knowledge base is an operating asset","category":"knowledge","dek":"A useful answer can change the work. A forgotten document cannot.","sections":[{"heading":"Value appears in use","paragraphs":["A knowledge base earns its place when someone uses it to make a better decision. Its size tells us very little on its own. Ten clear explanations that resolve recurring uncertainty can matter more than a thousand files whose purpose nobody remembers.","Consider the difference between storing a client specification and making that specification available beside the work it governs. The same file has a different operational value when the person checking a deliverable can find the relevant requirement without reconstructing the project history."]},{"heading":"Organize around questions","paragraphs":["Articles give explanations a durable home. Reference Files preserve source material. Folders and Data Tags help establish relationships and context. These are different jobs, and treating every piece of information as an interchangeable attachment makes the collection harder to use.","In OnPoint, these capabilities provide the ingredients for a knowledge base that participates in work. Start by asking what decisions recur: which version applies, what evidence is required, and why a method was chosen. Then organize the knowledge so those questions have dependable paths to answers."]},{"heading":"Stewardship creates the return","paragraphs":["An operating asset needs care. A document can become obsolete while remaining beautifully formatted. An authoritative answer can lose its basis when a requirement changes. Ownership and review are part of the value, not administrative tasks added afterward.","The aspiration is practical: when someone opens the knowledge base, they should encounter the accumulated judgment of the company. Useful structure, visible sources, and maintained explanations make that possible. AI can help people reach the material; the organization still has to make the material worth reaching."]}],"brief":{"summary":"A knowledge base becomes operationally valuable when people can retrieve maintained knowledge at a decision point.","workflow":["Identify a recurring decision","Organize its explanation and source files","Assign review responsibility"],"boundary":"Storage volume and AI availability do not establish accuracy, currency, or business value."},"features":["Articles","Reference Files","Folders","Data Tags"],"references":[],"url":"https://onpoint.ontel.co/blog/the-knowledge-base-is-an-operating-asset","markdownUrl":"https://onpoint.ontel.co/blog/the-knowledge-base-is-an-operating-asset/index.md"},{"slug":"an-article-is-a-place-for-understanding","title":"An article is a place for understanding","category":"knowledge","dek":"Give the reasoning a home, not just the conclusion.","sections":[{"heading":"Preserve the explanation","paragraphs":["A message can settle a question in the moment and still leave the next person confused. The participants know the background. They remember the tradeoffs. They understand what an informal phrase refers to. A reader arriving three months later has none of those advantages.","An article creates room to make the explanation stand on its own. What problem were we solving? Which conditions mattered? What did we decide, and what would make us reconsider? These questions turn a conclusion into knowledge someone else can use."]},{"heading":"Write for the next encounter","paragraphs":["In OnPoint, Articles belong to the Library and can carry the structured explanation that conversations often lack. Reference Files can preserve the original material, while related work supplies examples of how the guidance is used.","Suppose a team changes an inspection sequence. The article should explain the failure the change addresses, the new order, and the exceptions that require judgment. Copying the final chat message into a page is a start, but the work of explanation happens when the author makes the missing context explicit."]},{"heading":"Clarity is a contribution","paragraphs":["A good article reduces the amount of personal access required to do good work. People should not have to know the original author, attend the original meeting, or guess the right search term to understand a standard.","This is also why thoughtful writing matters in an AI-enabled system. Clear concepts and explicit boundaries give retrieval and summarization better material. The article is a contribution to future colleagues and to the tools helping them. Both benefit when the reasoning is visible."]}],"brief":{"summary":"Articles preserve explanations, decisions, and conditions so knowledge remains understandable outside its original conversation.","workflow":["Turn a recurring answer into an Article","Include rationale and exceptions","Connect supporting Reference Files"],"boundary":"AI retrieval cannot recover reasoning that was never documented."},"features":["Articles","Reference Files","Library"],"references":[],"url":"https://onpoint.ontel.co/blog/an-article-is-a-place-for-understanding","markdownUrl":"https://onpoint.ontel.co/blog/an-article-is-a-place-for-understanding/index.md"},{"slug":"reference-files-keep-the-world-in-the-record","title":"Reference files keep the world in the record","category":"knowledge","dek":"An explanation becomes stronger when its evidence stays close.","sections":[{"heading":"Keep the original","paragraphs":["A summary is useful because it leaves things out. That is also its limitation. A sentence saying that an installation looks correct cannot replace the photograph, drawing, or specification on which the assessment depends. Someone reviewing the conclusion needs a path back to the material.","Reference Files preserve that path. They let an organization keep the original artifact alongside its interpretation, so a later reader can inspect the basis of a claim rather than accepting a compressed account as the whole story."]},{"heading":"Separate evidence from interpretation","paragraphs":["Imagine a QA checklist asking whether an equipment label is readable. A photograph contains the evidence; a reviewer supplies the assessment. If an AI system cannot establish the serial number from the image, the appropriate result is uncertainty and a request for better evidence.","OnPoint's folder review model separates item findings, rationale, and source references from the human decision. That separation is an important design principle beyond QA. The file says what was captured. The assessment says what someone believes it establishes. Those two things should remain distinguishable."]},{"heading":"Make review possible","paragraphs":["Useful reference material needs enough context to be found and interpreted. Name it clearly, associate it with the relevant work, and explain what question it helps answer. A pile of attachments can preserve bytes while losing their significance.","A company gains more than storage when it keeps evidence close to decisions. It gains the ability to revisit an interpretation, resolve a disagreement, and improve a method without relying entirely on memory. The record remains open to a closer look."]}],"brief":{"summary":"Reference Files preserve source material separately from the assessments made about it.","workflow":["Attach the source file to the relevant work","State the criterion being assessed","Record the finding with its evidence"],"boundary":"A file or AI finding is not proof of a criterion unless the evidence actually supports it."},"features":["Reference Files","Checklists","Folders"],"references":[],"url":"https://onpoint.ontel.co/blog/reference-files-keep-the-world-in-the-record","markdownUrl":"https://onpoint.ontel.co/blog/reference-files-keep-the-world-in-the-record/index.md"},{"slug":"data-tags-are-a-language-for-the-business","title":"Data Tags are a language for the business","category":"knowledge","dek":"Shared meaning starts with agreeing what things are called.","sections":[{"heading":"Naming shapes what we can see","paragraphs":["Two teams can describe the same customer, location, or type of work in different ways. Each description may make sense locally. Together, they create friction: searches miss relevant records, reports divide what should be one group, and people spend time translating between departmental habits.","A shared vocabulary is a small piece of infrastructure with a large job. It gives information a recognizable shape across the places where work happens. The value comes from consistent meaning, not from adding the greatest number of labels."]},{"heading":"Start with useful distinctions","paragraphs":["Data Tags in OnPoint help give content structured context. A team might use a location, work category, or other relevant business distinction to make related material easier to organize and retrieve. The vocabulary should follow the questions people actually ask.","Before creating another tag, ask what decision it will support. Will it help locate evidence, distinguish a client requirement, or connect comparable work? If two labels mean the same thing, choosing one shared term is usually more useful than teaching everyone to search for both."]},{"heading":"Let the language evolve deliberately","paragraphs":["Businesses change, and their vocabulary must be able to change with them. That does not mean every new project needs a new taxonomy. It means someone takes responsibility for definitions, clarifies ambiguous terms, and considers how a change affects existing records.","AI makes this discipline more valuable. A system interpreting company information benefits from explicit relationships and consistent concepts. Tags cannot eliminate ambiguity, but they can make important distinctions visible. A better language for the business creates a better starting point for both human understanding and machine interpretation."]}],"brief":{"summary":"Data Tags provide structured business context that helps organize and interpret related information.","workflow":["Choose a recurring business distinction","Define a shared term","Apply and maintain it consistently"],"boundary":"Tags support interpretation; they do not guarantee automatic entity resolution or correct AI conclusions."},"features":["Data Tags","Articles","Folders"],"references":[],"url":"https://onpoint.ontel.co/blog/data-tags-are-a-language-for-the-business","markdownUrl":"https://onpoint.ontel.co/blog/data-tags-are-a-language-for-the-business/index.md"},{"slug":"folders-should-carry-context","title":"Folders should carry context","category":"knowledge","dek":"The container becomes useful when it explains the relationship.","sections":[{"heading":"A place is not yet a purpose","paragraphs":["A folder can be a convenient location for files and still tell a new colleague very little. Why are these items together? Which ones define the requirement? Which are evidence? What is missing? Organization becomes more useful when the grouping explains the work.","Think of a client handoff. The brief, checklist, reference images, and acceptance material are related because they support one outcome. Their relationship matters more than the fact that they happen to share a directory."]},{"heading":"Build a working context","paragraphs":["OnPoint's Folders bring structured content and review material into a shared context. Used thoughtfully, a folder can make the expectations and evidence around a piece of work easier to inspect. It becomes a useful place to start asking questions.","For a site review, begin with a clear purpose and the requirements that govern it. Include the files that support those requirements. Identify gaps explicitly. A missing acceptance document should not be hidden by the presence of many unrelated attachments."]},{"heading":"Make the next person welcome","paragraphs":["The quality of a working folder can be judged by a simple test: could a capable colleague understand what to do next without a private briefing? Some work will always require conversation, but the record should reduce avoidable reconstruction.","This is a larger principle of connected operations. Structure should help people inherit context, not merely inherit objects. When the purpose, evidence, and open questions travel together, a handoff becomes an invitation to continue the work with understanding."]}],"brief":{"summary":"Folders group the requirements, structured content, and evidence associated with a shared work context.","workflow":["Define the folder purpose","Gather requirements and supporting material","Make unresolved gaps visible"],"boundary":"Folder organization does not itself certify completeness or grant access to restricted material."},"features":["Folders","Reference Files","Checklists"],"references":[],"url":"https://onpoint.ontel.co/blog/folders-should-carry-context","markdownUrl":"https://onpoint.ontel.co/blog/folders-should-carry-context/index.md"},{"slug":"templates-are-lessons-you-can-start-from","title":"Templates are lessons you can start from","category":"knowledge","dek":"The next project should inherit what the previous one taught you.","sections":[{"heading":"Give learning a starting position","paragraphs":["A team learns something useful, writes it down, and then begins the next project from the same old blank page. The lesson exists, but the starting conditions have not changed. People must remember to find and apply it every time.","A template puts selected understanding where new work begins. It can carry the questions that are easy to forget, the sequence that has proved useful, and the structure that makes review easier. It turns a lesson into an available starting point."]},{"heading":"Preserve room for judgment","paragraphs":["Templates in OnPoint help teams reuse structure across work. The best template is explicit about what should remain consistent and where the next situation requires attention. A standard field is useful; an unexplained assumption repeated across every project is a liability.","For example, a handoff template might request supporting photos, the applicable specification, and an owner for unresolved questions. The team still decides which evidence is sufficient for this particular job. Reuse removes unnecessary setup without removing the need to think."]},{"heading":"Improve the inheritance","paragraphs":["When a project reveals that a template is missing a useful question, review the proposed change before making it the next default. The change should have a reason. Otherwise, templates accumulate fields until completing them becomes a task detached from the work.","A mature template is a conversation between past experience and present circumstances. It helps the company remember without pretending every future situation will be identical. That is how standardization can support progress: each new beginning has the chance to be better informed."]}],"brief":{"summary":"Templates make reviewed structure reusable at the beginning of similar work.","workflow":["Identify a repeated setup or omission","Revise a template with a clear rationale","Use it as the next starting point"],"boundary":"Template changes require deliberate review; reuse does not mean every situation is identical."},"features":["Templates","Checklists","Folders"],"references":[],"url":"https://onpoint.ontel.co/blog/templates-are-lessons-you-can-start-from","markdownUrl":"https://onpoint.ontel.co/blog/templates-are-lessons-you-can-start-from/index.md"},{"slug":"knowledge-needs-an-owner","title":"Knowledge needs an owner","category":"knowledge","dek":"A shared resource still needs someone to care whether it is right.","sections":[{"heading":"Shared does not mean self-maintaining","paragraphs":["A company can agree that knowledge belongs to everyone and still discover that nobody is responsible for keeping it useful. A procedure remains searchable long after the work has changed. A source file loses its relevance. New colleagues follow guidance that looks authoritative because no one has said otherwise.","Ownership gives shared knowledge a route to maintenance. It identifies who can evaluate a proposed correction, explain the current interpretation, and decide whether a reference is still suitable for use."]},{"heading":"Own the quality, share the understanding","paragraphs":["In an OnPoint knowledge workflow, the Article can hold the explanation and its supporting material can remain available for review. The operating practice around that content should identify a responsible person or team, especially where mistakes have meaningful consequences.","Ownership should not create a bottleneck in which only one person can contribute. A field colleague may notice the gap first. Another specialist may provide the evidence. The owner's job is to help the organization resolve the question and keep the resulting guidance coherent."]},{"heading":"Review where the cost of error is real","paragraphs":["Not every note needs the same maintenance schedule. A historical account and a current installation requirement have different consequences when they are outdated. Focus review effort on the knowledge people use to make consequential decisions.","The aspiration is a shared memory that remains trustworthy as the business changes. AI can make old material easier to find, which makes this care more necessary. Better access is valuable when the organization also knows how to challenge, correct, and maintain what is being accessed."]}],"brief":{"summary":"Knowledge stewardship assigns responsibility for maintaining explanations and evaluating corrections.","workflow":["Identify decision-critical guidance","Name a responsible reviewer in the working process","Review evidence when circumstances change"],"boundary":"This is an operating practice, not a claim that every Article has an automatic review schedule."},"features":["Articles","Library","Reference Files"],"references":[],"url":"https://onpoint.ontel.co/blog/knowledge-needs-an-owner","markdownUrl":"https://onpoint.ontel.co/blog/knowledge-needs-an-owner/index.md"},{"slug":"what-nasa-teaches-us-about-lessons-learned","title":"What NASA teaches us about lessons learned","category":"knowledge","dek":"A lesson needs a path from the original event to future practice.","sections":[{"heading":"Preserve the event and the recommendation","paragraphs":["NASA describes its Lessons Learned system as a collection in which lessons include the original driving event and recommendations. The agency connects that knowledge to improvement through training, practices, policies, and procedures. The useful idea is the relationship between experience and a changed way of working.","The lesson for an ordinary business is not to imitate the scale or assurance requirements of a space program. It is to ask whether learning has a destination. Where should a discovery go so it can affect the next relevant decision?"]},{"heading":"Give the lesson a usable form","paragraphs":["In OnPoint, an Article can explain an event, Reference Files can preserve the evidence, and a Checklist or Template can provide a place to apply a reviewed improvement. These are building blocks for a learning practice; they do not make that practice happen by themselves.","Imagine a recurring missing photograph at client handoff. The useful lesson is more specific than a reminder to be careful. It explains why the image matters, when it should be captured, and how a reviewer can determine whether it is usable."]},{"heading":"Close the loop in the work","paragraphs":["A lesson has not completed its journey when someone files it. Look at a subsequent job. Did the team ask the improved question? Was the evidence better? Did the change create an unexpected problem elsewhere?","That follow-through turns organizational memory into a working discipline. The ambition is not a museum of previous mistakes. It is a company in which one team's experience can improve another team's starting point, with the reasoning and evidence still available for inspection."]}],"brief":{"summary":"NASA provides an example of linking documented events and recommendations to future practice; OnPoint supplies building blocks for a business to establish its own learning loop.","workflow":["Describe the event with evidence","Review a specific recommendation","Apply and examine it in later work"],"boundary":"This is an analogy to a public learning practice, not a NASA endorsement or an aerospace-assurance claim."},"features":["Articles","Reference Files","Templates","Checklists"],"references":[{"label":"NASA: Lessons Learned","url":"https://www.nasa.gov/nasa-lessons-learned/","note":"Source for the description of NASA lesson records and their connection to improvement. The OnPoint application is our editorial interpretation."}],"url":"https://onpoint.ontel.co/blog/what-nasa-teaches-us-about-lessons-learned","markdownUrl":"https://onpoint.ontel.co/blog/what-nasa-teaches-us-about-lessons-learned/index.md"},{"slug":"the-right-to-understand-the-work","title":"The right to understand the work","category":"knowledge","dek":"Good systems make context available to the people expected to act.","sections":[{"heading":"Responsibility requires context","paragraphs":["It is difficult to take responsibility for a decision when the information behind it is scattered among conversations you did not attend. A person can be assigned the next step without receiving the understanding needed to carry it out well.","That gap is often treated as a communication problem. It is also a design problem. Where does the explanation live? Who can find it? Does the system make the relevant evidence available at the moment someone is expected to use judgment?"]},{"heading":"Make context part of the handoff","paragraphs":["OnPoint's connected approach brings knowledge and operational work into one environment. Articles can explain the method, Checklists can state expectations, and Reference Files can preserve the material a person needs to inspect. Chat remains valuable for discussion, but it should not be the only place the reason survives.","Consider a colleague taking over an unfamiliar client account. A list of tasks tells them what is pending. The client's requirements and the reasoning behind earlier decisions tell them how to act intelligently. Both belong in the handoff."]},{"heading":"Respect attention and agency","paragraphs":["Making context available does not mean exposing every record to everyone. People need the information they are permitted to use, organized around the responsibility they actually hold. Access boundaries and understandable explanations work together.","Our philosophical starting point is that people do better work when a system treats them as participants capable of judgment. A business operating system should support that participation. It should make it easier to understand the situation, question an assumption, and contribute an improvement that others can carry forward."]}],"brief":{"summary":"People need accessible, relevant context to exercise meaningful responsibility at work.","workflow":["State the responsibility","Provide the permitted requirements and rationale","Keep a route for questions and corrections"],"boundary":"Relevant context must respect access boundaries; shared understanding does not require universal access."},"features":["Articles","Checklists","Reference Files","Chat"],"references":[],"url":"https://onpoint.ontel.co/blog/the-right-to-understand-the-work","markdownUrl":"https://onpoint.ontel.co/blog/the-right-to-understand-the-work/index.md"},{"slug":"a-business-operating-system-connects-the-work","title":"A business operating system connects the work","category":"operations","dek":"The opportunity is in the relationships between the tools.","sections":[{"heading":"Follow one piece of work","paragraphs":["A customer request becomes a conversation. The conversation reveals a requirement. The requirement becomes a checklist. The checklist needs evidence. Someone reviews the evidence and decides what happens next. Viewed through a department chart, these can look like separate activities. Viewed through the work, they are one connected story.","A business operating system is our name for an environment designed around that continuity. The point is not the number of screens. It is whether the business can preserve meaning as work moves between them."]},{"heading":"Connect the different forms of context","paragraphs":["OnPoint brings communications, knowledge, activity, and performance into a shared platform. Articles, Folders, Checklists, Chat, and the broader product areas each contribute a different kind of context. Agents and advisors add ways to interpret permitted information and help people act on it.","An illustrative handoff makes the idea concrete. Keep the brief available, collect the evidence, identify the unresolved criterion, and let the next person inspect the same underlying material. Less of the work has to be recreated in a private explanation."]},{"heading":"Judge the continuity","paragraphs":["Integration should be judged at the seams. Can a person understand why a request exists? Can they find the relevant source? Can they tell what remains undecided? A collection of applications can share a login and still leave these questions unanswered.","Our ambition is a business that can move forward without constantly abandoning its context. The operating system is valuable when it helps people continue a shared process with understanding, even as responsibilities, locations, and tools change."]}],"brief":{"summary":"OnPoint uses business operating system to describe a shared environment connecting knowledge, communications, operational work, and AI assistance.","workflow":["Capture the request and its context","Connect requirements with evidence","Carry unresolved decisions into the handoff"],"boundary":"This describes product direction and connected capabilities, not universal integration with every external application."},"features":["Articles","Folders","Checklists","Chat","Agents","Advisors"],"references":[],"url":"https://onpoint.ontel.co/blog/a-business-operating-system-connects-the-work","markdownUrl":"https://onpoint.ontel.co/blog/a-business-operating-system-connects-the-work/index.md"},{"slug":"the-handoff-is-where-the-system-is-tested","title":"The handoff is where the system is tested","category":"operations","dek":"Work should change hands without losing its memory.","sections":[{"heading":"Transfer understanding","paragraphs":["A handoff can be administratively complete and operationally weak. The owner changes, the message is sent, and the task appears in the right queue. Yet the new owner still has to ask what the client meant, which specification applies, or why an earlier option was rejected.","The missing object is understanding. A good handoff transfers enough of it for the next person to continue responsibly. That requires more than an updated assignment field."]},{"heading":"Carry the open question forward","paragraphs":["In an OnPoint workflow, a Folder can collect the work context, a Checklist can make requirements visible, and Reference Files can preserve the evidence. Chat supplies the conversation that resolves ambiguity. The handoff should show both what is established and what remains uncertain.","Suppose a site is ready for a walkthrough except for one unreadable equipment label. Saying that the job is nearly complete hides the next decision. Linking the unresolved criterion and its photo tells the incoming colleague exactly where to look and why."]},{"heading":"Make acceptance meaningful","paragraphs":["The receiving person should be able to inspect the context, identify a gap, and ask for clarification. A handoff is a transfer between people, not a one-way declaration that the sender is finished.","This principle scales from field work to client service and internal projects. A strong system reduces the amount of reconstruction each transition demands. It allows responsibility to move while the evidence, reasoning, and unfinished questions remain attached to the work."]}],"brief":{"summary":"A useful handoff transfers relevant evidence, requirements, and unresolved decisions with responsibility.","workflow":["Gather the work context","Identify unresolved checklist items","Let the receiving person inspect and clarify"],"boundary":"The example illustrates a working practice; assignment alone does not establish acceptance or completeness."},"features":["Folders","Checklists","Reference Files","Chat"],"references":[],"url":"https://onpoint.ontel.co/blog/the-handoff-is-where-the-system-is-tested","markdownUrl":"https://onpoint.ontel.co/blog/the-handoff-is-where-the-system-is-tested/index.md"},{"slug":"checklists-make-expectations-visible","title":"Checklists make expectations visible","category":"operations","dek":"A clear criterion creates the possibility of a useful review.","sections":[{"heading":"Ask a question that can be answered","paragraphs":["A checklist item such as make sure everything is good feels reassuring until someone must determine whether it has been satisfied. The phrase hides several possible standards. Different reviewers can reach different conclusions without either person realizing they are answering a different question.","A useful checklist makes the expectation inspectable. The serial label is readable is a more precise criterion than equipment checked. It tells the person doing the work what evidence to capture and gives the reviewer a defined question."]},{"heading":"Link the criterion and the evidence","paragraphs":["OnPoint Checklists can structure the expectations around work, while Reference Files provide the material used in review. The QA demonstration on our use-cases page shows why those roles should remain distinct: a criterion may be covered, need review, or lack evidence.","A photo may establish that equipment is installed without establishing the serial number. The reviewer should not have to collapse those two judgments into one optimistic checkmark. Better questions make both success and uncertainty easier to describe."]},{"heading":"Let the checklist improve","paragraphs":["A checklist is a living expression of what the team believes matters. If a recurring failure reveals an omitted criterion, review the omission. If an item no longer supports a meaningful decision, reconsider its place.","The goal is a shared standard that helps people pay attention. A longer checklist is not automatically a stronger one. The useful measure is whether its criteria make the work clearer and its review more reliable, while leaving room for the judgment the situation requires."]}],"brief":{"summary":"Checklists express specific criteria; evidence and human review establish whether those criteria are satisfied.","workflow":["Write an observable criterion","Capture relevant evidence","Review coverage and uncertainty separately"],"boundary":"A completed checklist is not a guarantee of quality, compliance, or safety."},"features":["Checklists","Reference Files","Templates"],"references":[],"url":"https://onpoint.ontel.co/blog/checklists-make-expectations-visible","markdownUrl":"https://onpoint.ontel.co/blog/checklists-make-expectations-visible/index.md"},{"slug":"forms-turn-requests-into-a-starting-point","title":"Forms turn requests into a starting point","category":"operations","dek":"The first questions determine how much the next person has to reconstruct.","sections":[{"heading":"Design the arrival","paragraphs":["A request often arrives before it is ready to become work. The goal is unclear, the relevant file is missing, or the requester assumes everyone knows the background. The receiving team then performs an invisible second task: assembling the information needed to begin the first one.","A well-designed form makes that preparation visible. It asks the questions that genuinely affect routing, interpretation, and the next decision. It should help the requester explain the situation rather than demand an administrative performance."]},{"heading":"Ask with a purpose","paragraphs":["OnPoint includes Forms among the structured ways teams collect information. A useful intake pattern might ask what outcome is needed, which context applies, and what evidence is already available. The exact questions should follow the work, not a generic desire to collect more data.","Imagine a request for a site review. Location, the relevant checklist, and the supporting files can give the reviewer a much better beginning than an isolated message asking someone to take a look. Each field earns its place by reducing a real ambiguity."]},{"heading":"Leave room for the unexpected","paragraphs":["Structure has limits. A form cannot anticipate every exception, and forcing a novel situation into an unsuitable field can make the record less accurate. Give people room to explain what does not fit.","Good intake design respects both sides of the handoff. It reduces the burden on the person receiving the request while helping the person submitting it express what matters. The result is a clearer starting point for the business, with fewer assumptions hidden between the lines."]}],"brief":{"summary":"Forms collect structured context that can make incoming work easier to understand and route.","workflow":["Identify information needed to begin","Ask only decision-relevant questions","Preserve an explanation of exceptions"],"boundary":"A form collects input; it does not automatically validate the truth or completeness of every answer."},"features":["Forms","Folders","Reference Files"],"references":[],"url":"https://onpoint.ontel.co/blog/forms-turn-requests-into-a-starting-point","markdownUrl":"https://onpoint.ontel.co/blog/forms-turn-requests-into-a-starting-point/index.md"},{"slug":"surveys-should-start-a-conversation-with-reality","title":"Surveys should start a conversation with reality","category":"operations","dek":"Collecting answers matters when the organization is prepared to listen.","sections":[{"heading":"Make room for a different account","paragraphs":["A dashboard shows the measures a business has chosen to collect. A survey can ask about the experiences those measures leave out. What is difficult? Which instruction is unclear? Where does a process create unnecessary effort? The answers can challenge a comfortable interpretation of how the organization works.","That possibility is the reason to ask. If the result has already been decided, the survey becomes a ritual rather than a useful instrument."]},{"heading":"Connect feedback to the work","paragraphs":["OnPoint Surveys provide a way to collect responses within the broader operating environment. Their value depends on the questions, the audience, and what happens afterward. A short survey about a recent handoff can be more actionable than a sprawling questionnaire with no clear decision attached.","For example, ask whether the recipient had the information needed to continue, where they had to seek clarification, and which missing reference would have helped. These questions direct attention to the quality of the handoff instead of simply asking whether someone was satisfied."]},{"heading":"Interpret with care","paragraphs":["A response describes someone's perspective. It is evidence worth examining, not an automatic explanation of every cause. Compare it with the relevant work, discuss the pattern, and consider whose experience may be absent from the responses.","The aspiration is a company that can hear itself more clearly. Surveys create an opening for that conversation. Closing the loop means explaining what was learned, what will change, and what needs more investigation. Listening becomes credible when people can see its consequences."]}],"brief":{"summary":"Surveys collect perspectives that can inform operational improvement when interpreted with context.","workflow":["Ask about a specific experience","Examine responses alongside the work","Explain the resulting action or open question"],"boundary":"Survey responses are perspectives, not a representative or causal finding by default."},"features":["Surveys","Articles","Chat"],"references":[],"url":"https://onpoint.ontel.co/blog/surveys-should-start-a-conversation-with-reality","markdownUrl":"https://onpoint.ontel.co/blog/surveys-should-start-a-conversation-with-reality/index.md"},{"slug":"chat-is-where-work-thinks-out-loud","title":"Chat is where work thinks out loud","category":"operations","dek":"Keep conversation close, and give durable decisions somewhere to live.","sections":[{"heading":"Conversation reveals the unfinished thought","paragraphs":["Before a decision becomes a clean statement, it is often a conversation. Someone asks a question, another person supplies an exception, and a third notices a missing piece of evidence. Chat gives that unfinished thinking a place to happen quickly.","The risk comes when the conversation is also the only durable record. A later colleague sees the final instruction without the reasoning, or searches through a long thread without knowing which exchange resolved the issue."]},{"heading":"Connect discussion and knowledge","paragraphs":["OnPoint brings Chat and Conferencing into the same broader environment as operational work and the Library. That proximity supports a useful practice: discuss the uncertainty where the team can respond, then preserve the reviewed explanation where future readers can find it.","A client question may begin in a conversation and end in a revised checklist or an explanatory Article. The conversation and the durable record have different purposes. Keeping the relationship understandable helps the team retain both speed and memory."]},{"heading":"Respect the human medium","paragraphs":["Not every message should become an organizational artifact. People need room to explore, reconsider, and speak informally. The important design question is which decisions and lessons deserve a maintained record, and who takes responsibility for creating it.","A connected business does not need to turn every conversation into a document. It needs a dependable route from useful conversation to shared understanding. Chat is where work can think out loud; the knowledge base is where the parts worth carrying forward can become clear."]}],"brief":{"summary":"Chat supports live discussion; Articles and operational records can preserve the reviewed decisions that emerge from it.","workflow":["Discuss a concrete uncertainty","Resolve it with relevant evidence","Preserve the durable explanation in an Article"],"boundary":"This practice does not imply automatic meeting transcription or automatic conversion of every conversation into knowledge."},"features":["Chat","Conferencing","Articles","Checklists"],"references":[],"url":"https://onpoint.ontel.co/blog/chat-is-where-work-thinks-out-loud","markdownUrl":"https://onpoint.ontel.co/blog/chat-is-where-work-thinks-out-loud/index.md"},{"slug":"offline-work-is-still-company-work","title":"Offline work is still company work","category":"operations","dek":"The operating model should account for the places where connectivity runs out.","sections":[{"heading":"The work does not disappear","paragraphs":["A field colleague enters a location with unreliable connectivity. The client still expects progress. The equipment still needs attention. The requirement to preserve useful evidence remains. A system designed only for a perfect connection can leave the person doing the work outside the company's digital record.","Offline support begins by recognizing that disconnection is a real operating condition. It deserves explicit behavior, rather than an optimistic assumption that every action can reach the server immediately."]},{"heading":"Be precise about what is available","paragraphs":["OnPoint has offline capabilities for supported content and field workflows. That is a more useful description than saying the entire application works offline. Different actions depend on different data and services, and users need to understand those differences.","An appropriate field practice is to prepare the required material while connected, use the supported offline workflow, and confirm synchronization after returning to connectivity. The local state and the shared state may temporarily differ. Making that distinction visible matters."]},{"heading":"Reconnection is part of the workflow","paragraphs":["The job is not finished merely because a device accepted an action. The team needs to know whether the shared record received it and whether anything requires attention. A conflict or failed synchronization should be treated as an operational question to resolve.","The larger ambition is continuity between the office and the field. People should be able to contribute useful work where the business actually happens. That requires honest boundaries, clear preparation, and an explicit return path into the shared system."]}],"brief":{"summary":"OnPoint supports offline behavior for selected content and field workflows, with synchronization needed to update the shared record.","workflow":["Prepare supported content while connected","Complete the supported offline work","Confirm synchronization and resolve issues"],"boundary":"Offline Mode does not mean every page, AI service, or business action is available without connectivity."},"features":["Offline Mode","Reference Files","Folders"],"references":[],"url":"https://onpoint.ontel.co/blog/offline-work-is-still-company-work","markdownUrl":"https://onpoint.ontel.co/blog/offline-work-is-still-company-work/index.md"},{"slug":"map-lenses-turn-location-into-a-question","title":"Map Lenses turn location into a question","category":"operations","dek":"A map becomes more useful when it shows what you are trying to understand.","sections":[{"heading":"Choose the question before the view","paragraphs":["A map covered in markers can look informative while leaving the viewer uncertain about what deserves attention. Location is one dimension of the work. The useful view depends on the question: where are the relevant sites, which records belong to this area, or what context should a field team inspect?","A lens is a way of making that question explicit. Instead of treating every visible item as equally important, it selects a particular perspective on the information."]},{"heading":"Connect place and context","paragraphs":["OnPoint's Map Lenses are part of its approach to viewing operational information geographically. A map can help someone orient themselves, but the associated records and evidence give the location its meaning. The pin is an entrance to context, not the whole explanation.","Consider a team preparing work across several sites. A useful map view helps establish where the relevant work is. The linked operational context then explains the requirements and open questions that make each location different."]},{"heading":"Keep the view honest","paragraphs":["A map is always a representation of available information. Its usefulness depends on the records behind it, their recency, and the access the viewer has. A polished visual should not imply that the system knows more than those sources establish.","The aspiration is a business that can understand its work in place as well as in lists and documents. Geography can reveal relationships that are easy to overlook elsewhere. The lens makes the perspective intentional, and the underlying context makes it actionable."]}],"brief":{"summary":"Map Lenses provide selected geographic perspectives on available operational information.","workflow":["Choose a geographic question","Select the relevant map perspective","Inspect the context behind the visible records"],"boundary":"Map views depend on available, permitted data and do not imply universal live location tracking."},"features":["Map Lenses","Folders","Reference Files"],"references":[],"url":"https://onpoint.ontel.co/blog/map-lenses-turn-location-into-a-question","markdownUrl":"https://onpoint.ontel.co/blog/map-lenses-turn-location-into-a-question/index.md"},{"slug":"standard-work-can-be-a-platform-for-change","title":"Standard work can be a platform for change","category":"operations","dek":"A shared starting point makes an improvement easier to recognize.","sections":[{"heading":"Make the current method visible","paragraphs":["If every person performs a process differently and nobody can explain why, it is difficult to identify what an improvement actually changed. A shared method gives a team something concrete to examine. It makes variation discussable.","The Lean Enterprise Institute describes standardized work as a subject of continuing improvement through kaizen. The useful connection is that a standard can support learning rather than represent the end of learning."]},{"heading":"Preserve the reason for the method","paragraphs":["In OnPoint, Templates and Checklists can express repeatable structure, while Articles explain the reasoning and Reference Files preserve examples. Together, they can help a team distinguish a deliberate change from accidental drift.","Imagine revising the order of a site inspection because one observation is easier to make before another task is completed. The revised checklist gives the team a new sequence. The Article explains the operational reason, so the next person knows when the logic applies and when to ask for guidance."]},{"heading":"Review the result","paragraphs":["A changed template is a proposal about a better way to begin. Its usefulness should be examined in subsequent work. Did it reduce the omission? Did it introduce friction? Do the exceptions need a clearer explanation?","The philosophical point is that consistency and imagination can reinforce each other. A visible starting point gives improvement something to act upon. The organization can become more adaptable when it knows what it is changing, why it is changing it, and how it will learn from the result."]}],"brief":{"summary":"Shared standards provide a visible baseline for deliberate improvement; OnPoint Templates and Checklists can express that baseline.","workflow":["Document the current method and rationale","Review a proposed change","Examine its use in subsequent work"],"boundary":"The Lean connection is editorial analysis, not a claim of certification or guaranteed process improvement."},"features":["Templates","Checklists","Articles"],"references":[{"label":"Lean Enterprise Institute: Standardized Work","url":"https://www.lean.org/lexicon-terms/standardized-work/","note":"Source for the relationship between standardized work and continuous improvement. The OnPoint example is illustrative."}],"url":"https://onpoint.ontel.co/blog/standard-work-can-be-a-platform-for-change","markdownUrl":"https://onpoint.ontel.co/blog/standard-work-can-be-a-platform-for-change/index.md"},{"slug":"the-client-should-inherit-clarity","title":"The client should inherit clarity","category":"operations","dek":"A handoff package is a statement about how well the work is understood.","sections":[{"heading":"Deliver more than a collection of files","paragraphs":["A client receives a folder of documents and a message saying the job is complete. The package may contain everything required, yet still demand substantial interpretation. Which file answers which requirement? What changed? Is an unresolved issue significant or merely unfinished administration?","A clear handoff makes those relationships understandable. It helps the recipient inspect what was delivered and identify the decisions that remain. That clarity is part of the service, even when it is not a separate line on the invoice."]},{"heading":"Build the package from the work","paragraphs":["OnPoint's connected approach brings client context, requirements, supporting material, and conversation into the same operating environment. A handoff can be prepared from that context instead of assembled as a separate story after the fact.","For an illustrative site walkthrough, organize the checklist, relevant photos, and explanatory notes around the client's questions. If one requirement lacks evidence, say so. A package that clearly identifies a gap is more useful than a polished presentation that obscures it."]},{"heading":"Preserve the relationship after delivery","paragraphs":["The handoff may become the starting point for a future question, maintenance visit, or new project. A clear record helps the team return to the original context without relying on the same people being available.","The aspiration is a business whose work remains understandable after the immediate task is finished. Clients inherit clarity, and the company retains a dependable account of what it delivered. Both sides can move forward from the same evidence rather than from different recollections."]}],"brief":{"summary":"A clear client handoff maps deliverables and evidence to requirements and makes unresolved questions explicit.","workflow":["Organize material around client requirements","Explain the evidence and any gaps","Preserve the context for later questions"],"boundary":"The workflow does not imply automatic client access or acceptance; sharing and review remain deliberate."},"features":["Clients","Folders","Checklists","Reference Files"],"references":[],"url":"https://onpoint.ontel.co/blog/the-client-should-inherit-clarity","markdownUrl":"https://onpoint.ontel.co/blog/the-client-should-inherit-clarity/index.md"},{"slug":"compass-is-the-presence-between-intent-and-action","title":"Compass is the presence between intent and action","category":"intelligence","dek":"A place to begin with what you mean, rather than where you think the answer lives.","sections":[{"heading":"Begin with the intent","paragraphs":["People rarely think in navigation menus. They think that a client needs an answer, a checklist needs attention, or a colleague needs a clearer handoff. The first challenge is translating that intent into the right record, tool, and next step.","Compass represents a different starting point in OnPoint. It is a presence people can turn to across the application, with AI assistance connecting a question to accessible knowledge and supported tools. The ambition is to reduce the distance between understanding what you want and knowing how to proceed."]},{"heading":"An oracle with evidence","paragraphs":["We use The Oracle as a creative description of that presence. It is not a claim of omniscience. Useful assistance should show its relationship to the company's information and distinguish an answer from a proposed action.","The public Compass demonstration makes that sequence tangible: find a checklist, explain an evidence gap, and prepare a follow-up for review. These are different intentions. A dependable assistant should make the transition between them understandable rather than conceal action behind conversational fluency."]},{"heading":"Keep the person in the relationship","paragraphs":["The future we are interested in is a company whose knowledge becomes easier to consult and whose tools become easier to use through intent. That ambition does not remove access boundaries, supported-tool limits, or human judgment.","Compass should feel like an available intelligence within the system. Its value comes from helping a person see the relevant context and take an informed next step. The special presence becomes useful when it makes the business more understandable and the person's agency more effective."]}],"brief":{"summary":"Compass is OnPoint’s AI assistance surface for consulting accessible knowledge and using supported tools. The Oracle is editorial positioning.","workflow":["Find permitted context","Explain the relevant evidence","Review a supported proposed action"],"boundary":"Compass is not omniscient and cannot perform every possible app action. The public interaction is a demonstration."},"features":["Compass","Articles","Agents"],"references":[],"url":"https://onpoint.ontel.co/blog/compass-is-the-presence-between-intent-and-action","markdownUrl":"https://onpoint.ontel.co/blog/compass-is-the-presence-between-intent-and-action/index.md"},{"slug":"agents-and-advisors-have-different-jobs","title":"Agents and advisors have different jobs","category":"intelligence","dek":"Observation and execution belong in the same system, with clear roles.","sections":[{"heading":"Notice before acting","paragraphs":["A useful observation does not always call for an immediate automated action. A handoff may be approaching while an evidence gap remains unresolved. The appropriate first step may be to bring that relationship to a person's attention and let them examine the sources.","Advisors fit this role in OnPoint's operating model. They help surface observations, activity, and recommendations from permitted context. Their contribution is to direct attention toward something that may deserve judgment."]},{"heading":"Give execution a defined scope","paragraphs":["Agents concern the work that can be carried out through supported tools and workflows. Moving from an observation to execution requires a clearer contract: what action is proposed, what information it uses, and what approval or access is required.","Imagine an advisor noticing that a walkthrough is near and a checklist still lacks a readable label photo. Preparing a request for that photo is different from sending it. The system should make that difference visible to the person responsible for the work."]},{"heading":"Design the relationship","paragraphs":["The distinction is useful even when one interface helps coordinate both roles. An advisor can help a person understand why something matters. An agent can help carry out a supported next step. Compass can provide a place to express the intent connecting them.","The aspiration is an organization that receives thoughtful assistance without losing the ability to understand who decided what. Clear roles make the experience easier to trust. They also make failures easier to diagnose: was the observation wrong, the proposed action unsuitable, or the execution incomplete?"]}],"brief":{"summary":"Advisors surface observations and recommendations; agents assist with supported execution. The roles are related but distinct.","workflow":["Inspect an advisor observation","Review the proposed next step","Authorize supported execution where required"],"boundary":"An advisor prompt is not evidence that an action has occurred. Tool support and approval rules still apply."},"features":["Advisors","Agents","Compass"],"references":[],"url":"https://onpoint.ontel.co/blog/agents-and-advisors-have-different-jobs","markdownUrl":"https://onpoint.ontel.co/blog/agents-and-advisors-have-different-jobs/index.md"},{"slug":"how-ai-reads-a-qa-checklist","title":"How AI reads a QA checklist","category":"intelligence","dek":"A useful assessment connects each criterion to what the evidence can establish.","sections":[{"heading":"Start with the requirement","paragraphs":["A QA checklist gives the review its questions. Without those questions, an AI system might produce a fluent description of a file while missing the decision the team actually needs to make. The criterion establishes what the evidence is being asked to support.","Take a site handoff with three requirements: installation photos are attached, the equipment serial number is readable, and signed acceptance is present. These are separate claims. A photograph can support the first without resolving the second, and it cannot stand in for the third."]},{"heading":"Explain the finding","paragraphs":["OnPoint's folder AI-review model supports item-level findings, rationale, supporting or conflicting source references, and missing evidence. This makes the review more useful than an unexplained overall score. A person can inspect which criterion needs attention and what material the assessment relies on.","In the public demonstration, the equipment appears in the image but the label is obscured. The useful result is a needs-review finding with a clear explanation. The system should preserve uncertainty where the source cannot establish the answer."]},{"heading":"Keep the human result separate","paragraphs":["AI analysis is an input to review. It does not become the human checklist result merely because it is available. The reviewer needs the source, the reasoning, and the ability to accept or dismiss the reading in the application.","That separation gives AI a productive role: directing attention, organizing evidence, and explaining gaps. The final decision remains grounded in a person's examination of what the work requires and what the record actually shows."]}],"brief":{"summary":"OnPoint’s folder AI review compares checklist criteria with evidence and presents item-level rationale and source references for human review.","workflow":["Read each criterion","Compare it with the supplied sources","Review the AI finding separately from the human result"],"boundary":"AI may miss details or misinterpret evidence. The public QA example performs no real inference or record changes."},"features":["Checklists","Reference Files","Folders"],"references":[],"url":"https://onpoint.ontel.co/blog/how-ai-reads-a-qa-checklist","markdownUrl":"https://onpoint.ontel.co/blog/how-ai-reads-a-qa-checklist/index.md"},{"slug":"an-observation-can-change-the-day","title":"An observation can change the day","category":"intelligence","dek":"Sometimes the most useful assistance is the question you had not yet asked.","sections":[{"heading":"Bring the connection into view","paragraphs":["A conversation mentions a walkthrough tomorrow. A QA record contains an unresolved evidence question. Either fact may be easy to overlook on its own. Together, they suggest a concrete concern worth examining before the handoff.","An advisor becomes useful when it helps a person notice that relationship. The value is not an additional notification for its own sake. It is a timely explanation of why particular information may matter now."]},{"heading":"Show the basis of the prompt","paragraphs":["OnPoint's advisor model works with observations, activity, and recommendations. A good observation should make its basis inspectable. Which record contains the open question? What event makes it relevant? What is the proposed next step?","Our public advisor example connects an approaching walkthrough with an unreadable serial-label photo. The visitor can expand the evidence and preview a follow-up. That structure keeps the reasoning close to the suggestion, so the person can challenge the connection before deciding what to do."]},{"heading":"Earn the interruption","paragraphs":["Attention is limited. An observation should be relevant enough to justify interrupting the person receiving it. Repeating a fact they already know without offering useful context creates noise, even when the notification contains an AI-generated sentence.","The aspiration is a system that helps people maintain perspective while the business keeps moving. Advisors should contribute to that perspective through clear, grounded observations. The person remains free to inspect, dismiss, or act, and the record should distinguish the suggestion from the resulting decision."]}],"brief":{"summary":"Advisor observations connect permitted information to a reason for human attention and a reviewable next step.","workflow":["Identify a relevant observation","Inspect its supporting records","Decide whether a follow-up is warranted"],"boundary":"An observation may be incomplete or mistaken. It does not prove urgency or authorize action."},"features":["Advisors","Checklists","Chat"],"references":[],"url":"https://onpoint.ontel.co/blog/an-observation-can-change-the-day","markdownUrl":"https://onpoint.ontel.co/blog/an-observation-can-change-the-day/index.md"},{"slug":"retrieval-is-part-of-the-answer","title":"Retrieval is part of the answer","category":"intelligence","dek":"The quality of assistance begins before the first sentence is generated.","sections":[{"heading":"Ask what the answer had access to","paragraphs":["Two assistants can receive the same question and produce different answers because they were given different context. One sees a maintained procedure and the current reference file. The other sees an old note and an incomplete conversation. Fluency cannot repair that difference on its own.","In a business setting, the path to the source is part of the quality of the answer. Which material was retrieved, whether it is relevant, and whether the person is permitted to use it all matter."]},{"heading":"Give knowledge a usable shape","paragraphs":["OnPoint's Ask capabilities work with permitted sources and citations. Articles, Reference Files, and structured context provide material that people and AI can consult. Clear titles, explicit terms, and maintained explanations improve the starting conditions for retrieval.","Suppose someone asks what evidence is needed for a handoff. The answer should be grounded in the relevant requirements, rather than a generic description of what handoffs usually contain. A source reference lets the person inspect that connection and see whether the answer fits the actual work."]},{"heading":"Treat citations as an invitation","paragraphs":["A citation is valuable because it provides a route to verification. It does not automatically prove that the cited passage supports every sentence in an answer. The reader still needs to examine the relationship between the claim and the source.","The ambition is accessible intelligence with an inspectable foundation. Better retrieval, better knowledge stewardship, and clear source relationships work together. The most confident-sounding answer is less useful than one that helps the person understand both what is established and what remains uncertain."]}],"brief":{"summary":"Source retrieval supplies the context for an AI answer; citations help people inspect the connection between claims and permitted material.","workflow":["Find the relevant permitted sources","Generate a contextual answer","Inspect the cited evidence"],"boundary":"A citation does not by itself guarantee that an answer is correct or fully supported."},"features":["Compass","Ask","Articles","Reference Files"],"references":[],"url":"https://onpoint.ontel.co/blog/retrieval-is-part-of-the-answer","markdownUrl":"https://onpoint.ontel.co/blog/retrieval-is-part-of-the-answer/index.md"},{"slug":"ai-amplifies-the-system-around-it","title":"AI amplifies the system around it","category":"intelligence","dek":"Organizational design belongs in the AI conversation.","sections":[{"heading":"Look beyond the model","paragraphs":["DORA's 2025 research on AI-assisted software development describes AI as an amplifier of existing organizational strengths and weaknesses. Its focus is software delivery, so it should not be treated as direct proof about every type of business. It does offer a useful question: what operating conditions are we asking AI to amplify?","A system with clear ownership, maintained knowledge, and visible evidence gives assistance a different foundation from one with conflicting procedures and untraceable decisions. Buying access to a model does not resolve those differences."]},{"heading":"Improve the surrounding conditions","paragraphs":["OnPoint's approach places AI alongside communications, knowledge, activity, and operational context. The product thesis is that these relationships matter to useful assistance. The practical work includes clarifying requirements, maintaining Articles, organizing Reference Files, and making human review understandable.","Imagine introducing an advisor into a process where nobody knows which checklist is current. The advisor may surface information faster, but the organization still has to resolve the underlying ambiguity. Better assistance and better operating discipline should develop together."]},{"heading":"Evaluate the whole arrangement","paragraphs":["A meaningful AI evaluation asks more than whether an answer sounded good. Could the person inspect its sources? Did it help identify the right next decision? Was the proposed action within scope? Did the workflow remain understandable afterward?","Our inference from the industry conversation is that organizational infrastructure deserves as much attention as model capability. The aspiration is a business ready to use intelligence well, with the context and habits that let assistance improve the work rather than accelerate its confusion."]}],"brief":{"summary":"DORA’s software-delivery research motivates an editorial argument that AI adoption should include improvements to organizational context and practice.","workflow":["Examine current knowledge and ownership","Introduce a bounded AI workflow","Evaluate its effect on real decisions"],"boundary":"The DORA findings concern software development. This article’s broader business application is an inference, not a measured OnPoint result."},"features":["Articles","Advisors","Checklists"],"references":[{"label":"DORA: State of AI-assisted Software Development 2025","url":"https://dora.dev/research/2025/dora-report/","note":"Source for the amplifier framing in software delivery. Broader implications and OnPoint examples are editorial analysis."}],"url":"https://onpoint.ontel.co/blog/ai-amplifies-the-system-around-it","markdownUrl":"https://onpoint.ontel.co/blog/ai-amplifies-the-system-around-it/index.md"},{"slug":"a-proposal-is-a-powerful-interface","title":"A proposal is a powerful interface","category":"intelligence","dek":"Make an intended change understandable before it becomes a fact.","sections":[{"heading":"Put the next step on the table","paragraphs":["An assistant that can prepare an action gives a person something concrete to review. That is different from merely explaining how an action might be performed. It is also different from carrying it out without making the consequences clear.","A proposal occupies a useful space between intention and execution. It can show the target, the relevant content, and the reason for the change while the person still has the opportunity to revise or decline it."]},{"heading":"Keep the boundary visible","paragraphs":["OnPoint's AI tool model includes supported actions and reviewable proposals. The public Compass example uses a follow-up request to show the distinction. Preparing a request for a clearer photo does not mean the message has been sent, an assignment has changed, or a checklist result has been updated.","A useful proposal tells the person what will happen if they proceed. The more consequential the action, the more important it is that the target and scope are understandable. Familiar language can help, but a friendly tone should never substitute for clarity."]},{"heading":"Make collaboration concrete","paragraphs":["Proposals give people and AI a practical way to collaborate. The assistant can assemble context and reduce setup effort. The person can apply judgment, correct a mistaken assumption, or decide that another action is better suited to the situation.","The ambition is a system in which intelligence makes action easier to consider, not harder to inspect. A proposal can be an excellent interface because it turns an abstract intention into a specific, reviewable possibility while preserving the person's ability to choose."]}],"brief":{"summary":"A reviewable AI proposal describes an intended supported action before execution.","workflow":["Express the desired outcome","Inspect the proposed target and change","Approve, revise, or decline as supported"],"boundary":"Prepared, approved, and executed are different states. A proposal is not a completed action."},"features":["Compass","Agents","Advisors"],"references":[],"url":"https://onpoint.ontel.co/blog/a-proposal-is-a-powerful-interface","markdownUrl":"https://onpoint.ontel.co/blog/a-proposal-is-a-powerful-interface/index.md"},{"slug":"writing-company-knowledge-for-ai-readers","title":"Writing company knowledge for AI readers","category":"intelligence","dek":"Machines benefit from the same clarity that helps a new colleague.","sections":[{"heading":"State the subject explicitly","paragraphs":["An article that repeatedly refers to this, that, and the process may be perfectly clear to its author and difficult for an outside reader to interpret. AI retrieval can expose that weakness because a passage may be encountered separately from the conversation that produced it.","Write down the subject. Name the capability, explain the problem it addresses, and identify the conditions under which the explanation applies. The purpose is not to stuff a page with keywords. It is to make the meaning survive a new context."]},{"heading":"Separate fact, example, and aspiration","paragraphs":["This Journal gives each article a visible reference brief alongside the essay. The brief summarizes the concept, provides an illustrative workflow, and states a boundary. Product descriptions, industry evidence, and our philosophy have different roles, and a reader should be able to distinguish them.","For example, Compass can be described as an AI assistance surface with supported tools. The Oracle is a creative interpretation of its role. A fictional handoff illustrates the interaction. None of those statements should be flattened into a claim that Compass knows everything or can execute every action."]},{"heading":"Make verification easy","paragraphs":["Useful writing gives the reader a stable page, clear headings, source links where relevant, and a way to return to the full explanation. A machine-readable version should preserve the same substance instead of presenting a more aggressive set of claims to automated readers.","The ambition is accurate understanding wherever the article is encountered. A person skimming a page and an AI system retrieving a passage should find compatible accounts of what the business does, why it matters, and what the material does not establish."]}],"brief":{"summary":"AI-readable company knowledge uses explicit subjects, stable references, and clear distinctions between product facts, examples, and aspirations.","workflow":["Define the concept","State the product relationship and example","Include limitations and source references"],"boundary":"Clear formatting can help interpretation but cannot guarantee AI ingestion, citation, ranking, or accuracy."},"features":["Articles","Compass","Library"],"references":[],"url":"https://onpoint.ontel.co/blog/writing-company-knowledge-for-ai-readers","markdownUrl":"https://onpoint.ontel.co/blog/writing-company-knowledge-for-ai-readers/index.md"},{"slug":"an-ai-readable-business-has-an-explicit-vocabulary","title":"An AI-readable business has an explicit vocabulary","category":"intelligence","dek":"Define the relationships before asking a machine to reason across them.","sections":[{"heading":"Do not make the reader guess","paragraphs":["A business develops shorthand over time. A client nickname, an internal acronym, or a phrase such as final pack may carry a rich meaning for experienced colleagues. To a new person or an AI system, it may be an unexplained token.","An explicit vocabulary makes the important concepts and relationships visible. What is a checklist in this workflow? Which file supplies evidence? What distinguishes an advisor observation from an authorized action? These definitions reduce avoidable ambiguity."]},{"heading":"Give concepts stable homes","paragraphs":["OnPoint combines several kinds of working information. Articles explain. Reference Files preserve source material. Data Tags provide structured context. Folders group related work. Agents and advisors contribute different kinds of assistance. Defining those roles helps readers understand the system without relying on a promotional label.","An AI reference article should also describe relationships. A QA finding concerns a particular criterion and refers to evidence. A proposed follow-up concerns an unresolved question. A human decision remains distinct from the suggestion that informed it."]},{"heading":"Keep the vocabulary accountable","paragraphs":["Definitions should evolve when the product or practice changes. A clear but outdated description can be more misleading than an obviously incomplete one. Treat terminology as maintained knowledge, with visible dates and a connection to the current explanation.","The aspiration is a company whose information can be interpreted consistently across people and tools. That begins with ordinary editorial work: name the things, describe how they relate, and say where the explanation stops. Intelligence has a better foundation when the organization makes its own meaning explicit."]}],"brief":{"summary":"Explicit definitions and relationships help human and AI readers interpret OnPoint concepts consistently.","workflow":["Name the capability","Describe its relationship to other records","Maintain the definition as behavior changes"],"boundary":"An editorial definition is not an executable API contract or a guarantee of feature availability in every configuration."},"features":["Articles","Data Tags","Folders","Advisors"],"references":[],"url":"https://onpoint.ontel.co/blog/an-ai-readable-business-has-an-explicit-vocabulary","markdownUrl":"https://onpoint.ontel.co/blog/an-ai-readable-business-has-an-explicit-vocabulary/index.md"},{"slug":"useful-ai-knows-where-the-answer-stops","title":"Useful AI knows where the answer stops","category":"intelligence","dek":"Uncertainty can be the most actionable part of an assessment.","sections":[{"heading":"Leave the gap visible","paragraphs":["An equipment photo shows the installation clearly but leaves the serial label blurred. A system can describe the visible equipment and still be unable to answer the checklist criterion. The missing answer is not a failure to be concealed. It is information about what the team needs next.","A useful assistant should make that boundary understandable. The evidence supports one statement and leaves another unresolved. Collapsing both into a confident overall judgment makes the work harder to review."]},{"heading":"Turn uncertainty into a question","paragraphs":["OnPoint's QA review model provides ways to express missing evidence and item-level rationale. That creates a practical route from uncertainty to the next decision. A person can inspect the source, ask for a better image, or determine that another record resolves the question.","The same principle applies beyond QA. A retrieved article may be relevant but outdated. An advisor may observe a pattern without knowing its cause. A proposed action may depend on a permission or fact the system has not established."]},{"heading":"Make restraint useful","paragraphs":["The goal is not an assistant that avoids every difficult question. It is an assistant that distinguishes what it can establish from what requires further evidence or human judgment. That distinction helps the person direct the next effort intelligently.","Our aspiration is practical confidence built on inspectable reasons. A system that can say what remains unknown can help a business move forward more responsibly than one that fills every silence with a plausible sentence. Sometimes the most useful answer is a well-framed request for the missing fact."]}],"brief":{"summary":"Explicit uncertainty identifies where available evidence cannot establish an answer and helps frame the next review step.","workflow":["Identify what the source supports","State the unresolved criterion","Seek the missing evidence or human judgment"],"boundary":"AI uncertainty labels are themselves fallible and require review in consequential work."},"features":["Checklists","Reference Files","Advisors","Compass"],"references":[],"url":"https://onpoint.ontel.co/blog/useful-ai-knows-where-the-answer-stops","markdownUrl":"https://onpoint.ontel.co/blog/useful-ai-knows-where-the-answer-stops/index.md"},{"slug":"connected-does-not-mean-open-to-everyone","title":"Connected does not mean open to everyone","category":"governance","dek":"Shared context becomes useful when its boundaries remain clear.","sections":[{"heading":"Connection needs a shape","paragraphs":["The promise of a connected business is not that every person sees every record. A client document, an internal discussion, and a restricted operational decision can belong to the same organization without belonging to the same audience.","A useful operating system must preserve these distinctions while still helping people find the context they are permitted to use. Otherwise, integration creates a choice between fragmentation and indiscriminate exposure that the business should not have to accept."]},{"heading":"Apply the boundary to assistance","paragraphs":["OnPoint's access model governs people and the information available to AI assistance. Asking a question should not become a shortcut around the permissions that apply to the underlying sources. The assistant's usefulness depends partly on respecting that context.","Consider a colleague preparing a handoff. They may need the project requirements and approved reference material without needing unrelated private records. A clear boundary gives the person enough context to do the work while preserving the restrictions that the organization has established."]},{"heading":"Make access understandable","paragraphs":["Permissions can become difficult to reason about when they are treated only as a technical concern. Teams also need a practical understanding of which information is appropriate for which audience and why. The operating practice should support that understanding.","The aspiration is confident connection. People can work across functions and consult shared knowledge without assuming that organizational membership grants universal visibility. A strong system lets context travel along legitimate relationships while keeping the boundaries of responsibility intact."]}],"brief":{"summary":"OnPoint connects information while applying access boundaries to people and AI-assisted retrieval.","workflow":["Identify the information needed for a responsibility","Apply the appropriate access scope","Consult only permitted context"],"boundary":"Connected information is not universally visible, and AI assistance does not override source permissions."},"features":["Access","Compass","Articles","Folders"],"references":[],"url":"https://onpoint.ontel.co/blog/connected-does-not-mean-open-to-everyone","markdownUrl":"https://onpoint.ontel.co/blog/connected-does-not-mean-open-to-everyone/index.md"},{"slug":"governance-belongs-inside-the-work","title":"Governance belongs inside the work","category":"governance","dek":"The moment of decision is where control becomes meaningful.","sections":[{"heading":"Put the question where it arises","paragraphs":["A policy can be carefully written and still have little influence on a rushed decision. The person doing the work may not know which part applies, may lack the relevant evidence, or may discover the approval requirement after the action has already happened.","Governance becomes more useful when the system helps make those conditions visible during the workflow. What is the person allowed to do? Which evidence supports the decision? What needs review before the business proceeds?"]},{"heading":"Connect the operating controls","paragraphs":["OnPoint combines permissions, traceable activity, requirements, and human review across its operating environment. These capabilities provide places to express governance in the work itself. Their value depends on how the organization uses them and whether the surrounding responsibilities are clear.","For example, an AI-proposed follow-up should make its intended action understandable before execution. A QA finding should remain distinct from the human result. A restricted source should remain restricted even when someone asks a convenient question about it."]},{"heading":"Make control support progress","paragraphs":["Good governance should help people act with confidence inside a clear scope. If every ordinary decision requires improvised permission seeking, the organization has not necessarily become more controlled. It may simply have made responsibility harder to exercise.","Our ambition is a system in which the rules, evidence, and decision rights are available where they matter. That makes governance part of the way a business operates and grows, rather than a separate account constructed after the work is finished."]}],"brief":{"summary":"Operational governance makes permissions, evidence, review requirements, and decision rights visible within workflows.","workflow":["Define the decision and its scope","Present evidence and review requirements","Record the resulting action"],"boundary":"Software controls support governance but do not by themselves establish regulatory compliance or organizational accountability."},"features":["Access","Checklists","Agents","Audit"],"references":[],"url":"https://onpoint.ontel.co/blog/governance-belongs-inside-the-work","markdownUrl":"https://onpoint.ontel.co/blog/governance-belongs-inside-the-work/index.md"},{"slug":"what-nist-adds-to-the-ai-conversation","title":"What NIST adds to the AI conversation","category":"governance","dek":"Trustworthy AI requires attention to the surrounding system.","sections":[{"heading":"Use a broader frame","paragraphs":["The NIST AI Risk Management Framework organizes its core around Govern, Map, Measure, and Manage. Its companion playbook offers suggested actions for organizations using the framework. These resources are voluntary guidance, not a certification attached to an individual product.","The useful shift is to consider AI as part of an operating arrangement with people, context, and consequences. A model's capability is one part of that arrangement. The surrounding decisions determine how it will actually be used."]},{"heading":"Ask operational questions","paragraphs":["For a business using OnPoint, the practical questions include what information an assistant can access, how a person reviews a finding, and what separates a proposed action from an executed one. These are ordinary workflow questions with governance consequences.","An illustrative QA review makes the connection tangible. The system should identify the requirement, preserve the evidence, expose uncertainty, and keep the human decision understandable. A useful review asks whether these relationships remain clear, not just whether the generated explanation reads well."]},{"heading":"Make the guidance your own","paragraphs":["A framework cannot substitute for examining the specific use case. Different actions have different consequences, and different sources carry different limitations. The organization must decide how to assess those conditions and what controls are appropriate.","Our editorial view is that AI governance should develop alongside AI capability. Clear access, traceable proposals, and reviewable evidence are practical design priorities. They are a starting point for disciplined use, not a claim that OnPoint has been certified by NIST or that a framework eliminates risk."]}],"brief":{"summary":"NIST AI RMF offers a voluntary frame for considering AI risk across governance, context, measurement, and management.","workflow":["Define the AI use case","Examine access, evidence, and review","Evaluate and maintain the controls appropriate to the situation"],"boundary":"This article describes a public framework and an editorial application. It is not compliance advice or a NIST certification claim."},"features":["Access","Compass","Checklists","Audit"],"references":[{"label":"NIST AI RMF Playbook","url":"https://www.nist.gov/itl/ai-risk-management-framework/nist-ai-rmf-playbook","note":"Source for the four functions and voluntary playbook guidance. The OnPoint workflow discussion is our interpretation."}],"url":"https://onpoint.ontel.co/blog/what-nist-adds-to-the-ai-conversation","markdownUrl":"https://onpoint.ontel.co/blog/what-nist-adds-to-the-ai-conversation/index.md"},{"slug":"a-history-of-changes-is-a-history-of-decisions","title":"A history of changes is a history of decisions","category":"governance","dek":"A useful record helps the next person understand how the present came to be.","sections":[{"heading":"Preserve the path","paragraphs":["A record shows the current state. A history can show the path that produced it. That difference matters when someone asks why a requirement changed, which interpretation was used, or whether an earlier version explains a disagreement.","Without a dependable path, people reconstruct events from memory and disconnected messages. Even when everyone acts in good faith, their recollections may emphasize different parts of the story."]},{"heading":"Keep the explanation with the change","paragraphs":["OnPoint includes revision and activity concepts that help preserve a trace of work. A useful operating practice adds the reason for a meaningful change, especially when it affects the way other people should act.","Suppose an Article is revised after a QA review identifies a recurring ambiguity. The updated text is useful. The explanation of the change is useful too: it helps a later reader understand which problem the revision addresses and why the previous wording was insufficient."]},{"heading":"Use history to improve understanding","paragraphs":["A change record should support learning as well as accountability. It can help a team see where a misunderstanding entered the process, recognize a deliberate correction, and avoid repeating an earlier debate without its evidence.","The aspiration is an organization whose decisions remain understandable beyond the moment they are made. A history cannot capture every thought, and a log is not automatically a complete explanation. But preserving the relevant events and rationale gives the business a stronger foundation for review, correction, and continuity."]}],"brief":{"summary":"Revision and activity records help preserve the path to a current state, especially when paired with a reason for meaningful changes.","workflow":["Record the relevant change","Explain its rationale","Use the history when reviewing later questions"],"boundary":"An activity log is not automatically a complete decision record or a legally sufficient audit trail."},"features":["Articles","Audit","Activity"],"references":[],"url":"https://onpoint.ontel.co/blog/a-history-of-changes-is-a-history-of-decisions","markdownUrl":"https://onpoint.ontel.co/blog/a-history-of-changes-is-a-history-of-decisions/index.md"},{"slug":"human-review-is-a-design-material","title":"Human review is a design material","category":"governance","dek":"People can only exercise judgment over what the interface makes understandable.","sections":[{"heading":"Design for the actual decision","paragraphs":["Adding an approval button does not necessarily create meaningful oversight. A person must understand what they are being asked to approve, which sources support it, and what will happen afterward. Without that context, the control can become a ritual click.","Human review belongs in the design of the workflow from the beginning. It affects how evidence is presented, how uncertainty is described, and how the proposed action is separated from the current state."]},{"heading":"Put the relevant pieces together","paragraphs":["OnPoint's QA demonstration places the checklist criterion, AI finding, rationale, and source reference near one another. The human result remains distinct. This arrangement gives the reviewer a clearer object of judgment than an isolated recommendation.","The same principle applies to Compass proposals. A person reviewing a follow-up needs to see what is being prepared and why. If the assistant has made a mistaken assumption about the work, the interface should make that assumption easier to notice."]},{"heading":"Preserve the ability to disagree","paragraphs":["A useful review process allows someone to reject the suggestion without losing the underlying context. The person may need to ask another question, inspect a different file, or choose a better next step. Disagreement is part of collaboration, not an exception to it.","Our aspiration is AI assistance that strengthens people's capacity to judge. The system can reduce the effort of gathering and organizing information while leaving the decision legible. Meaningful control comes from understanding the proposal, not merely being the last person to touch it."]}],"brief":{"summary":"Meaningful human review requires understandable evidence, scope, consequences, and the ability to disagree with a suggestion.","workflow":["Present the finding and source together","Explain the proposed change","Let the reviewer accept, revise, or dismiss as supported"],"boundary":"An approval control alone does not establish effective oversight. Review quality depends on the workflow and reviewer context."},"features":["Checklists","Compass","Agents","Reference Files"],"references":[],"url":"https://onpoint.ontel.co/blog/human-review-is-a-design-material","markdownUrl":"https://onpoint.ontel.co/blog/human-review-is-a-design-material/index.md"},{"slug":"performance-needs-an-explanation","title":"Performance needs an explanation","category":"governance","dek":"A number can show movement without telling you what changed.","sections":[{"heading":"Ask what the measure means","paragraphs":["A dashboard reports that completion increased. That may be useful, but it leaves several questions open. Was the work comparable? Did the definition change? Did quality improve, remain stable, or become harder to observe? A measure is a view of the business, not the business in its entirety.","Performance becomes more actionable when people can connect the number to the activity and context behind it. The question is not merely whether a value moved, but what decision the movement should inform."]},{"heading":"Keep outcomes close to evidence","paragraphs":["OnPoint's business operating system thesis brings performance into the same conversation as knowledge, activity, and work. The ambition is to make a result easier to inspect alongside the conditions that produced it.","For example, a team considering a new checklist should examine more than how quickly people complete it. Look at the clarity of the criteria, the quality of the supporting material, and the unresolved questions that remain at handoff. Those observations can explain whether the change is helping."]},{"heading":"Protect against easy conclusions","paragraphs":["A metric should not become an unsupported judgment about a person's character or contribution. People work under different conditions, and operational records are often incomplete. Review the context and make the limits of the comparison explicit.","The aspiration is informed management. A useful system helps people move from observation to a better question, and from that question to a considered decision. Performance data becomes more valuable when it is part of an explanation that can be challenged and improved."]}],"brief":{"summary":"Performance measures need definitions and operational context before they can support a reliable decision.","workflow":["Define the measure","Examine the related work and evidence","Consider alternative explanations before acting"],"boundary":"A metric alone does not establish causality, individual merit, or a fair comparison."},"features":["Dashboards","Activity","Checklists","Articles"],"references":[],"url":"https://onpoint.ontel.co/blog/performance-needs-an-explanation","markdownUrl":"https://onpoint.ontel.co/blog/performance-needs-an-explanation/index.md"},{"slug":"the-system-should-make-correction-easier","title":"The system should make correction easier","category":"governance","dek":"A business learns faster when changing its mind has a clear path.","sections":[{"heading":"Expect the first account to be incomplete","paragraphs":["A requirement can be misunderstood. A file can be mislabeled. A well-intended explanation can omit an important exception. These are ordinary possibilities in organizational work. A dependable system should provide a way to correct the record without making the correction harder than the original entry.","The design question is what happens when someone notices the problem. Can they find the relevant source? Can they explain the discrepancy? Does the person responsible for the record have enough context to review it?"]},{"heading":"Preserve the reason for revision","paragraphs":["OnPoint's Articles, Reference Files, and review workflows provide material for that conversation. A proposed correction becomes easier to assess when it identifies the exact statement or criterion and supplies the evidence that challenges it.","Imagine a checklist interpretation that treats a blurred photograph as sufficient. A reviewer can point to the unreadable detail and explain why another image is needed. The useful correction is specific. It improves the decision without requiring a sweeping accusation about the entire process."]},{"heading":"Reward a clearer account","paragraphs":["A culture of correction needs more than software. People must believe that raising a well-founded concern will help the work rather than merely create interpersonal risk. The system can support that culture by making evidence, revisions, and decisions understandable.","Our ambition is a company that can become more accurate over time. The ability to preserve a record matters, but so does the ability to improve it. Organizational memory should retain the path of learning while making the current understanding easier to use."]}],"brief":{"summary":"A correction workflow connects a specific disputed statement or finding with evidence and a responsible review.","workflow":["Identify the precise issue","Supply the relevant evidence","Review and record the correction"],"boundary":"Software can support correction, but it does not create a learning culture or resolve every disagreement automatically."},"features":["Articles","Reference Files","Checklists"],"references":[],"url":"https://onpoint.ontel.co/blog/the-system-should-make-correction-easier","markdownUrl":"https://onpoint.ontel.co/blog/the-system-should-make-correction-easier/index.md"},{"slug":"authority-should-not-be-hidden-in-a-prompt","title":"Authority should not be hidden in a prompt","category":"governance","dek":"A convincing sentence is not permission to change the business.","sections":[{"heading":"Separate language from authority","paragraphs":["An AI assistant receives many kinds of text: a person's request, a reference document, a conversation, and its own generated explanation. These sources do not have the same authority. A sentence inside a file should not become an instruction to override the organization's controls simply because a model can read it.","The distinction matters most when assistance can lead to action. Understanding a request and being authorized to execute it are separate questions."]},{"heading":"Make the action contract explicit","paragraphs":["OnPoint's approach to AI assistance includes permitted context, supported tools, and reviewable actions. The public showcase illustrates that contract by separating an observation, a prepared follow-up, and a person's decision. It does not present generated text as an independent source of permission.","In practice, a user may ask for a change that requires access they do not have, or a source may contain irrelevant instructions. The operating system should apply its controls through the action path, rather than relying on the tone or confidence of a response."]},{"heading":"Keep accountability outside the prose","paragraphs":["An explanation can help a person understand what an assistant proposes. The authority to act should remain grounded in the application's permissions and the applicable review process. This is a design principle that must be implemented and tested, not a property conferred by a carefully worded prompt.","The aspiration is powerful assistance within a comprehensible system. AI can help translate intent into a supported next step while the business retains an explicit account of who may authorize that step and what the system actually did."]}],"brief":{"summary":"AI-generated or retrieved text does not itself confer permission; supported actions must respect application access and review controls.","workflow":["Identify the requested action","Check the applicable authority","Present and execute only the supported authorized step"],"boundary":"This is a design principle, not a claim that prompt injection or every authorization risk has been eliminated."},"features":["Compass","Agents","Access"],"references":[],"url":"https://onpoint.ontel.co/blog/authority-should-not-be-hidden-in-a-prompt","markdownUrl":"https://onpoint.ontel.co/blog/authority-should-not-be-hidden-in-a-prompt/index.md"},{"slug":"a-source-link-is-an-invitation-to-check","title":"A source link is an invitation to check","category":"governance","dek":"Traceability is useful when someone can follow the reasoning back.","sections":[{"heading":"Make the connection inspectable","paragraphs":["A claim with a source is easier to examine than a claim without one. But the presence of a link is only the beginning. The reader still needs to determine whether the material actually supports the statement and whether the statement fits the current situation.","This is particularly important when AI summarizes several records. A source may be relevant to the topic without establishing the precise conclusion that appears in the answer."]},{"heading":"Keep the claim specific","paragraphs":["OnPoint's source-grounded assistance and item-level review concepts make it possible to keep evidence near a finding. A precise criterion helps the reviewer evaluate that relationship. The equipment is visible and the serial number is readable are different claims, even when they concern the same photograph.","The same discipline applies to this Journal. Industry sources support particular statements about research or public frameworks. Our broader interpretation is identified as an editorial view. A source should not be used to borrow authority for claims it never examined."]},{"heading":"Help the next reader verify","paragraphs":["Good evidence presentation reduces unnecessary effort. Name the source, explain why it matters, and keep a route to the original. When the evidence is incomplete or the conclusion is an inference, say so plainly.","The aspiration is a company whose explanations can withstand a closer look. Traceability supports that ambition when it gives people a practical route to verification and disagreement. A link becomes valuable through the relationship it makes visible between a statement and its foundation."]}],"brief":{"summary":"Source references support verification when they connect a specific claim with material that actually bears on it.","workflow":["State the claim precisely","Identify the supporting source","Inspect the claim-source relationship"],"boundary":"A source link is not an endorsement, a proof of causality, or a guarantee that an AI summary is correct."},"features":["Reference Files","Articles","Compass"],"references":[],"url":"https://onpoint.ontel.co/blog/a-source-link-is-an-invitation-to-check","markdownUrl":"https://onpoint.ontel.co/blog/a-source-link-is-an-invitation-to-check/index.md"},{"slug":"grow-without-losing-the-thread","title":"Grow without losing the thread","category":"governance","dek":"Scale should extend the company’s understanding, not dilute it.","sections":[{"heading":"Notice what growth changes","paragraphs":["A small team can coordinate through proximity. People remember the same client conversations and know whom to ask about an exception. As the organization grows, that informal network becomes harder for every new colleague to access.","The challenge is not simply adding more seats to the software. It is preserving the relationship between responsibility, knowledge, and evidence as more people participate in the work."]},{"heading":"Make the operating context portable","paragraphs":["OnPoint brings the building blocks of that context into a shared environment. Articles preserve explanations. Templates help new work inherit structure. Checklists clarify expectations. Access controls define appropriate visibility. These capabilities support a company in making its operating knowledge less dependent on personal proximity.","Imagine a second team taking on work previously handled by the founders. They need the standards and the reasons behind them, alongside a route to ask questions and propose improvements. Copying a task list gives them only part of that inheritance."]},{"heading":"Scale the ability to contribute","paragraphs":["A growing company should make room for new people to improve its methods, not merely reproduce them. A shared system is valuable when it helps a newcomer understand the current practice and contribute evidence that makes it better.","The aspiration is growth with continuity and participation. The company can extend its capacity while retaining the thread of what it has learned. That requires maintained knowledge, clear decision rights, and a willingness to keep the shared understanding open to review."]}],"brief":{"summary":"Scaling operating knowledge requires portable explanations, reusable structure, and clear responsibility across a growing organization.","workflow":["Document methods and rationale","Provide appropriate access and reusable structure","Let new teams question and improve the practice"],"boundary":"A shared platform supports growth but does not guarantee organizational alignment or a particular financial outcome."},"features":["Articles","Templates","Checklists","Access"],"references":[],"url":"https://onpoint.ontel.co/blog/grow-without-losing-the-thread","markdownUrl":"https://onpoint.ontel.co/blog/grow-without-losing-the-thread/index.md"},{"slug":"assets-are-the-inventory-of-the-organization","title":"Assets are the inventory of the organization","category":"future","dek":"A business should be able to reason about what it actually has.","sections":[{"heading":"Make the resources visible","paragraphs":["An asset is not only something installed at a job site. An organization depends on equipment, devices, and other resources distributed across its people and places. Decisions about work become harder when that inventory exists only in scattered spreadsheets or individual memory.","The larger idea behind Assets in OnPoint is an organizational inventory. It gives the business a place to represent the resources it manages, with the context needed to understand them. The field is one setting in which those resources are used, not the boundary of the concept."]},{"heading":"Add the context that decisions need","paragraphs":["OnPoint asset records include types, status, assignment, locations, attachments, custom fields, and Data Tags. Those details can make an inventory more useful than a list of names. They help establish what an item is, where it belongs, and how it relates to the organization.","Imagine planning work that requires a particular device. Knowing that the company owns one is different from knowing whether it is assigned, available, or recorded as needing maintenance. The record should help a person inspect the distinction before committing to a plan."]},{"heading":"Build toward organizational awareness","paragraphs":["Our ambition is for the system and its AI assistance to factor the organization's resources into relevant decisions. That requires maintained records, appropriate access, and supported connections between inventory and the decision being made.","An inventory becomes strategic when it improves the company's understanding of its own possibilities and constraints. The aim is a business that can ask what it needs to do next while remaining aware of what it already has to work with."]}],"brief":{"summary":"Assets is OnPoint’s organizational inventory, with typed records and context such as status, assignment, location, attachments, custom fields, and Data Tags.","workflow":["Record the organizational resource","Maintain its operational context","Consult the relevant inventory when planning work"],"boundary":"Not every AI workflow automatically consults every asset. Awareness depends on maintained records, access, and supported tools."},"features":["Assets","Data Tags","Reference Files","Compass"],"references":[],"url":"https://onpoint.ontel.co/blog/assets-are-the-inventory-of-the-organization","markdownUrl":"https://onpoint.ontel.co/blog/assets-are-the-inventory-of-the-organization/index.md"},{"slug":"availability-is-a-question-of-context","title":"Availability is a question of context","category":"future","dek":"Owning a resource and being able to use it are different facts.","sections":[{"heading":"Look beyond the count","paragraphs":["An organization may own several devices and still be unable to use any of them for a particular job. One is assigned elsewhere, another requires maintenance, and a third lacks the relevant capability. A count establishes existence. It does not establish suitability.","This is why an inventory should carry context. The decision about a resource depends on its characteristics, status, assignment, and the requirements of the work. Removing those relationships can make a seemingly simple answer misleading."]},{"heading":"Give the inventory a decision role","paragraphs":["OnPoint Assets provides records with types, custom fields, status, assignments, locations, and supporting material. A useful operating practice keeps the details relevant to planning current enough to consult. The record becomes part of the decision rather than a separate administrative afterthought.","For example, a coordinator preparing a review might inspect whether the necessary equipment is recorded as available and whether its documentation fits the task. If the record is stale or incomplete, that uncertainty should become a question for the responsible person."]},{"heading":"Make the ambition explicit","paragraphs":["The future opportunity is to connect inventory context with AI-assisted planning and recommendations where the tools support it. That could help people ask better questions about the resources a plan assumes. It is an ambition that depends on explicit integration and dependable underlying data.","A business becomes more self-aware when it can distinguish what exists from what is usable here and now. The value of an asset record lies partly in preserving those distinctions, so people can plan around real conditions rather than an optimistic total."]}],"brief":{"summary":"Asset availability and suitability depend on contextual records, not merely inventory counts.","workflow":["Identify the task requirements","Inspect asset status and relevant attributes","Confirm uncertain or outdated information"],"boundary":"The article does not claim automatic resource scheduling, procurement optimization, or real-time accuracy for every asset."},"features":["Assets","Data Tags","Reference Files"],"references":[],"url":"https://onpoint.ontel.co/blog/availability-is-a-question-of-context","markdownUrl":"https://onpoint.ontel.co/blog/availability-is-a-question-of-context/index.md"},{"slug":"the-end-of-reconstructing-the-company-every-morning","title":"The end of reconstructing the company every morning","category":"future","dek":"What if the first task of the day was understanding the next move?","sections":[{"heading":"Begin from a shared account","paragraphs":["Many workdays start with reconstruction. Read the messages, find the latest file, ask what changed, and determine which account is current. Some of that orientation is unavoidable. Much of it exists because the business has no dependable way to carry context across the boundary between yesterday and today.","The aspiration of a business operating system is a different beginning. The person should be able to encounter the relevant work, its recent activity, and the knowledge needed to decide what deserves attention."]},{"heading":"Connect the signals without erasing detail","paragraphs":["OnPoint brings communications, activity, knowledge, and operational records into the same environment. Advisors can help surface observations, while Compass provides a place to ask questions and consult accessible context. These capabilities support orientation when the underlying records are maintained and the assistance is relevant.","Imagine returning to a client handoff after a day away. The useful starting point is not an undifferentiated stream of updates. It is an understandable account of what changed, which requirement remains unresolved, and where the supporting material can be inspected."]},{"heading":"Spend attention on the decision","paragraphs":["A system should help people move from orientation to judgment without pretending that a summary contains everything. The route back to the source remains important, especially when the next action is consequential.","The future we want is not a business without conversation or discovery. It is a business that preserves enough continuity for people to spend more of their attention on the decision in front of them. Yesterday's context should become today's starting point."]}],"brief":{"summary":"Connected records and relevant AI assistance can support daily orientation by preserving context across time.","workflow":["Review the relevant activity","Inspect unresolved work and sources","Choose the next decision"],"boundary":"This is a product ambition and workflow illustration, not a measured time-saving claim or an automatic daily briefing guarantee."},"features":["Activity","Advisors","Compass","Chat"],"references":[],"url":"https://onpoint.ontel.co/blog/the-end-of-reconstructing-the-company-every-morning","markdownUrl":"https://onpoint.ontel.co/blog/the-end-of-reconstructing-the-company-every-morning/index.md"},{"slug":"attention-is-an-operating-resource","title":"Attention is an operating resource","category":"future","dek":"A system earns its place when it helps people see what matters.","sections":[{"heading":"Count the cost of interruption","paragraphs":["Microsoft's 2025 research on the infinite workday describes fragmented work using aggregated Microsoft 365 activity and survey evidence. Its findings concern the population and methods in that research. The broader question for a business is how its own systems distribute attention.","A notification can be useful, but receiving more signals is not the same as understanding the situation better. Every interruption asks a person to decide whether it matters, and that decision itself is work."]},{"heading":"Give observations a reason","paragraphs":["OnPoint's advisor concept should be understood against that constraint. An observation earns attention when it connects relevant information, explains why it may matter, and provides a route to the evidence. Repeating an event in a more elaborate sentence does not necessarily add value.","Consider an approaching handoff with an unresolved checklist criterion. A useful prompt explains the connection and lets the person inspect the sources. It gives attention a specific object instead of simply adding another item to the stream."]},{"heading":"Design for considered action","paragraphs":["The aspiration is assistance that improves perspective. People need room to focus, time to examine consequential decisions, and confidence that a signal carries meaningful context. More automation should not automatically mean more demands on their awareness.","Our editorial view is that attention belongs in the design of a business operating system as deliberately as information and permissions. A connected company should become easier to understand, not merely more capable of telling everyone that something happened."]}],"brief":{"summary":"Attention is a limited operating resource; relevant observations should explain why a signal matters and provide supporting context.","workflow":["Identify the reason for attention","Show the relevant evidence","Let the recipient decide whether to act"],"boundary":"Microsoft’s research is industry context, not evidence of OnPoint performance or a universal interruption rate."},"features":["Advisors","Activity","Chat"],"references":[{"label":"Microsoft WorkLab: Breaking down the infinite workday","url":"https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday","note":"Industry context on fragmented work. The OnPoint design argument is editorial interpretation, with no performance claim."}],"url":"https://onpoint.ontel.co/blog/attention-is-an-operating-resource","markdownUrl":"https://onpoint.ontel.co/blog/attention-is-an-operating-resource/index.md"},{"slug":"the-company-as-a-learning-institution","title":"The company as a learning institution","category":"future","dek":"Everyday work can create a shared capacity to understand.","sections":[{"heading":"Treat experience as a contribution","paragraphs":["A company is often described through its products, people, or financial results. It can also be understood as a place where experience is converted into collective capability. A person encounters a problem, develops an explanation, and makes that explanation available to others.","That conversion is not automatic. It depends on the opportunity to reflect, a place to preserve the lesson, and a route for the lesson to influence later work. Without those conditions, experience remains isolated even when the company is busy."]},{"heading":"Give learning an operating form","paragraphs":["OnPoint's Library, Templates, Checklists, and connected work provide places for understanding to become usable. An Article can explain what was learned. A Template can carry a reviewed improvement into a new project. A Checklist can make the updated expectation visible.","The useful question is whether those pieces form a living practice. Are people encouraged to improve the explanation? Can someone challenge a conclusion with better evidence? Does new work actually encounter the material the previous team created?"]},{"heading":"Make growth intellectual as well as operational","paragraphs":["The aspiration is a company that becomes more capable of understanding its own work. Growth can mean more than handling a larger volume of tasks. It can mean asking better questions, making better distinctions, and giving more people access to the knowledge needed to contribute.","A business operating system should support that possibility. It should make ordinary experience easier to preserve, examine, and reuse, so that the organization develops a shared capacity that extends beyond the memory of any one person."]}],"brief":{"summary":"A learning institution turns individual experience into maintained knowledge and changed practice across the organization.","workflow":["Capture a useful explanation","Review it with evidence","Apply and refine it through subsequent work"],"boundary":"This is an organizational philosophy, not a claim that software alone creates learning or guarantees better decisions."},"features":["Library","Articles","Templates","Checklists"],"references":[],"url":"https://onpoint.ontel.co/blog/the-company-as-a-learning-institution","markdownUrl":"https://onpoint.ontel.co/blog/the-company-as-a-learning-institution/index.md"},{"slug":"integration-is-a-human-experience","title":"Integration is a human experience","category":"future","dek":"The architecture matters because someone has to continue the work.","sections":[{"heading":"Follow the person across the seam","paragraphs":["A technical integration can successfully move data while leaving a person uncertain about what it means. The record arrived, but its purpose is unclear. The identifier matches, but the reason for the decision is missing. The systems are connected at one level and disconnected at another.","The human test is whether someone can continue the work with understanding. That test belongs alongside technical correctness, because both affect the usefulness of the system."]},{"heading":"Preserve relationships, not just fields","paragraphs":["OnPoint's operating-system idea centers on relationships between communications, knowledge, activity, and work. A requirement becomes more useful when the evidence and discussion around it remain understandable. A client record becomes more useful when it helps explain the decisions affecting that client.","Imagine receiving a handoff that contains every required file but no account of the open question. The data transfer is complete. The handoff still needs an explanation. Integration should reduce that gap rather than simply move it to another screen."]},{"heading":"Build for continuity","paragraphs":["This is why the design of navigation, references, and review surfaces matters. They determine how much context a person can carry from one part of the system to another. A shared login is convenient, but continuity is a deeper product responsibility.","The aspiration is a business whose systems respect the way people understand and act. Technical connections provide the foundation. The experience becomes meaningful when those connections help someone recognize the situation, inspect the evidence, and make the next considered move."]}],"brief":{"summary":"Humanly useful integration preserves the context and relationships needed to continue work across tools and responsibilities.","workflow":["Trace a real handoff","Identify the context lost at each transition","Connect the explanation with the transferred records"],"boundary":"This principle does not imply that OnPoint integrates with every external tool or automatically preserves every relationship."},"features":["Chat","Articles","Clients","Folders"],"references":[],"url":"https://onpoint.ontel.co/blog/integration-is-a-human-experience","markdownUrl":"https://onpoint.ontel.co/blog/integration-is-a-human-experience/index.md"},{"slug":"from-data-creation-to-organizational-understanding","title":"From data creation to organizational understanding","category":"future","dek":"More information creates an opportunity only when meaning can keep up.","sections":[{"heading":"Separate production from understanding","paragraphs":["A business can create more information than it knows how to interpret. Messages, files, forms, and activity records accumulate because work is happening. Their presence does not automatically produce a clearer account of the company.","The important transition is from information being generated to information being usable. What does a record describe? Which decision does it support? How does it relate to other material? These questions create the path from data to understanding."]},{"heading":"Give the information a connected home","paragraphs":["OnPoint brings communications, knowledge, activity, and performance into a shared operating environment. The premise is that these forms of information become more useful when people can inspect their relationships rather than repeatedly reconstruct them.","A checklist result, for example, gains meaning from the criterion, the evidence, and the review behind it. An activity event gains meaning from the work it concerns. The system should help retain those relationships as the volume of records grows."]},{"heading":"Make AI part of the interpretation","paragraphs":["AI can help retrieve, summarize, and examine permitted material through supported workflows. Its usefulness depends on the clarity and quality of that material. A larger context window cannot replace an explanation the organization never wrote or resolve a definition nobody agreed upon.","The aspiration is a business in which the rate of understanding can keep pace with the rate of activity. That requires more than collecting data. It requires structure, stewardship, and tools that help people connect the information to the decisions that matter."]}],"brief":{"summary":"Organizational understanding requires structure and relationships that make generated data useful for decisions.","workflow":["Identify the purpose of a record","Connect it to requirements and evidence","Use permitted AI assistance to inspect the context"],"boundary":"More data and more AI capacity do not automatically produce accurate understanding or better decisions."},"features":["Data Tags","Articles","Activity","Compass"],"references":[],"url":"https://onpoint.ontel.co/blog/from-data-creation-to-organizational-understanding","markdownUrl":"https://onpoint.ontel.co/blog/from-data-creation-to-organizational-understanding/index.md"},{"slug":"the-next-interface-is-a-better-question","title":"The next interface is a better question","category":"future","dek":"Intent can become a starting point for exploring the whole system.","sections":[{"heading":"Let the person begin with the problem","paragraphs":["Traditional navigation asks a person to know where the answer lives before they can ask for it. That is reasonable for familiar work, but it can be a barrier when the question crosses product areas. A client concern may involve conversation, evidence, requirements, and an available resource at the same time.","An intent-based interface starts with what the person is trying to understand or accomplish. It can help them discover the relevant context and the supported tools without demanding that they first memorize the application's structure."]},{"heading":"Keep the journey visible","paragraphs":["Compass expresses this ambition within OnPoint. A person can turn to an AI assistance surface while the broader system provides the knowledge and action capabilities behind it. The interaction should remain understandable as it moves from a question toward a possible next step.","The public demonstration uses finding a checklist, examining an evidence gap, and preparing a follow-up. Each step reveals a different kind of assistance. The person can see the connection between the request and the response instead of experiencing a mysterious leap from language to action."]},{"heading":"Preserve other ways to work","paragraphs":["A conversational interface does not make every other interface obsolete. A table may be better for comparing many records. A map may be better for geographic orientation. A detailed review surface may be better for inspecting evidence.","The aspiration is choice with continuity. People can begin with a question and move into the appropriate view when they need more control. Intelligence should help them reach the work in a form that suits the decision, rather than force every decision into a conversation."]}],"brief":{"summary":"Intent-based assistance helps people locate relevant context and supported actions while preserving specialized interfaces for detailed work.","workflow":["Express the question","Find the relevant permitted context","Move into the appropriate review or action surface"],"boundary":"Compass does not replace every interface, and natural-language requests remain limited by supported tools and access."},"features":["Compass","Map Lenses","Checklists","Assets"],"references":[],"url":"https://onpoint.ontel.co/blog/the-next-interface-is-a-better-question","markdownUrl":"https://onpoint.ontel.co/blog/the-next-interface-is-a-better-question/index.md"},{"slug":"what-a-business-should-remember","title":"What a business should remember","category":"future","dek":"The useful memory is the one that helps the next person think.","sections":[{"heading":"Choose what deserves to endure","paragraphs":["Not everything that happens in a company deserves equal weight in its shared memory. A temporary coordination message and a hard-earned explanation of a recurring failure have different future value. Saving both is possible; making the distinction clear is the editorial work.","A useful memory preserves what helps someone understand a decision, perform a responsibility, or improve a method. It should also retain enough evidence to question the explanation when circumstances change."]},{"heading":"Remember reasons and exceptions","paragraphs":["OnPoint's Articles and Reference Files provide places to preserve the reasoning and material behind the work. Templates and Checklists can carry selected understanding into repeatable practice. The relationship between those forms matters more than the number of records in any one of them.","For example, a team may remember that a particular photo is required without remembering why. The explanation of the requirement helps a future colleague handle a situation in which the usual image cannot be captured. Reasons create room for informed judgment; instructions alone can be brittle."]},{"heading":"Leave the memory open","paragraphs":["A maintained knowledge base should be able to change when new evidence arrives. Remembering is not the same as treating every past conclusion as permanent. A company can preserve the history of a decision while improving its current account.","The aspiration is memory that supports thought. People should inherit enough understanding to act responsibly and enough freedom to contribute a better explanation. A business becomes more capable when its past is available as a resource rather than imposed as an unquestionable answer."]}],"brief":{"summary":"Useful organizational memory preserves reasons, evidence, and exceptions that help future people exercise judgment.","workflow":["Identify knowledge with future decision value","Preserve its rationale and evidence","Revise the explanation when circumstances change"],"boundary":"Not every conversation should become permanent guidance, and old knowledge is not automatically current authority."},"features":["Articles","Reference Files","Templates","Checklists"],"references":[],"url":"https://onpoint.ontel.co/blog/what-a-business-should-remember","markdownUrl":"https://onpoint.ontel.co/blog/what-a-business-should-remember/index.md"},{"slug":"operate-govern-grow-as-one-system","title":"Operate, govern, and grow as one system","category":"future","dek":"The daily work, its boundaries, and its future belong in the same conversation.","sections":[{"heading":"Three questions about the same business","paragraphs":["How do we carry out the work? How do we keep it within the right boundaries? How do we become more capable over time? These questions are often assigned to different teams, but they concern the same organization and depend on much of the same information.","Operations creates activity and evidence. Governance defines responsibilities and decision rights. Growth depends partly on what the company learns and can reuse. Treating them as unrelated conversations makes it harder to see those connections."]},{"heading":"Give the system a shared foundation","paragraphs":["OnPoint brings communications, knowledge, activity, performance, and organizational records into one operating environment. Articles preserve understanding. Assets describe resources. Checklists clarify expectations. Agents, advisors, and Compass offer forms of assistance around permitted context and supported actions.","An illustrative client handoff contains all three questions. The team completes the work, reviews evidence within the appropriate authority, and preserves a lesson that can improve the next handoff. The same event can contribute to execution, control, and learning."]},{"heading":"Build a company that can continue","paragraphs":["The aspiration is not a business in which software makes every decision. It is a business in which people can understand the situation, act with appropriate authority, and leave useful knowledge for those who follow.","Operate, govern, and grow is therefore more than a list of product themes. It describes a connected ambition: the work moves forward, the boundaries remain understandable, and the organization becomes better prepared for what comes next. A business operating system should help keep those purposes in view together."]}],"brief":{"summary":"OnPoint’s operate, govern, and grow thesis connects execution, decision boundaries, and organizational learning around shared context.","workflow":["Carry out work with relevant context","Review evidence and authority","Preserve improvements for the next cycle"],"boundary":"This is an editorial synthesis of the product direction, not a guarantee of autonomous operation, compliance, or growth."},"features":["Articles","Assets","Checklists","Agents","Advisors","Compass"],"references":[],"url":"https://onpoint.ontel.co/blog/operate-govern-grow-as-one-system","markdownUrl":"https://onpoint.ontel.co/blog/operate-govern-grow-as-one-system/index.md"}]}