Legal

Program Forgemaster Service Terms

Last updated: · Effective

These Service Terms add to our Terms of Service for Program Forgemaster (forgemaster.vektorforgeai.com), our program management Platform. They are part of the Agreement, and words such as Platform, Your Content, owner, editor, viewer, export, download, plan limits, AI features, AI output, pre-release feature and multi-factor authentication have the meanings in the Terms of Service. If these Service Terms conflict with the Terms of Service, these Service Terms control for Program Forgemaster, as section 1 of the Terms of Service says. How we handle the information involved is described in our Privacy Policy.

1. Early access

Program Forgemaster is in early access: it is a pre-release feature under section 13 of the Terms of Service. We add people to early access by invitation, and an account we add has a Program Forgemaster plan. You sign in with your VektorForgeAI account, which needs multi-factor authentication. During early access there is no charge for Program Forgemaster. Before paid plans start, we will publish its plans and pricing and tell early access users, and section 4 of the Terms of Service will then apply. Features may change, move or be withdrawn while we work with early users.

2. Your programs

  • Who can see a program. A program, and everything in it, is visible only to its owner and the people the owner shares it with, as section 3 describes.
  • Product Architect is optional. You can start and run a program without Product Architect. If you also use Product Architect, the owner or a program manager can link a project to a product there by pasting its address. Program Forgemaster reads that product only when you import from it. You approve each import in Product Architect, and it copies the product’s charter, outcomes and releases into your program as items for you to review. Program Forgemaster never changes anything in Product Architect and keeps no ongoing access to it. Only the product’s owner, or someone the owner lets export, can import a product.
  • Importing projects from a CSV file. The owner or a program manager can also add projects from a CSV file they choose. Program Forgemaster reads the file in your browser and saves its rows as projects in your program. It doesn’t keep the file, doesn’t send it to our AI provider, and treats every cell as plain text, so formulas in the file are never run. Rows that can’t be imported are listed with the reason, and the rest are added.
  • Charter template and review. You can choose which charter sections are required for programs your account creates. Each new program copies that list when it’s created, and changing your template later doesn’t change existing programs. Only you see your template; everyone who can see a program sees which of its sections are required. The owner or a program manager can mark a charter ready for review, and while it’s in review it can’t be edited unless it’s moved back to draft. A charter can’t go for review or be approved until every required section is filled in. While a charter is in review, its sponsor, the owner or a program manager can approve it; the program’s history records who approved it and when. Only the owner or a program manager can mark it ready for review, move it back to draft or reopen it. Flint never marks a charter ready for review or approves it; people do.

3. Sharing and roles

The owner shares a program by inviting people by email. Everyone needs their own VektorForgeAI account with multi-factor authentication; there are no link-only shares. Each person has one role in a program:

  • Owner. The account that created the program, or that it was handed over to. The owner can do everything below, and is the only one who can share the program, change people’s roles, projects, download permission and access end dates, remove people, hand the program over and delete it. The owner can’t also be a member of their own program.
  • Program manager. Can edit the whole program, record the outcome of a decision and use Flint. Can’t share the program, delete it or hand it over.
  • Project manager. Can edit the projects the owner gives them and the roadmap items, RAID items, dependencies and benefit links tied to those projects, can comment and can use Flint. Can read the rest of the program.
  • Sponsor. Can read the program, comment, record the outcome of a decision that is waiting for an answer, and approve the charter while it is in review.
  • Viewer. Can read the program. Viewers can’t comment or record decisions.

In the words of the Terms of Service, program and project managers are editors, and sponsors and viewers are viewers. Commenting, recording a decision and approving a charter in review are the limited actions section 2 of the Terms of Service lets these Service Terms give to sponsors. A program can be shared with up to 50 people, counting invitations that haven’t been answered yet.

4. Who pays

  • Sponsors and viewers are free. They don’t need a Program Forgemaster plan of their own.
  • Program and project managers are covered by the owner’s plan while it is active, and don’t need a plan of their own. Plans may limit the number of program and project managers in a program.
  • If the owner’s plan ends, program and project managers can only read the program, and editing and Flint are paused for them, until the owner has a plan again. Sponsors and viewers keep their access. The owner needs a Program Forgemaster plan to open and change a program they own. A plan ending doesn’t delete the program.

5. Invitations, access and leaving

  • Invitations. An invitation can be accepted only by someone signed in to a VektorForgeAI account, with multi-factor authentication, whose email address matches the one the invitation was sent to. The program appears in their account only after they accept it. An invitation that isn’t answered expires after 30 days; we send one reminder after 7 days. The owner can send an invitation again, which starts a new 30 days, or cancel it. The person invited can decline it.
  • Access end dates. The owner can set a date when a person’s access ends, and change or clear it at any time. Access in Program Forgemaster doesn’t expire because it goes unused; it ends only on a date the owner sets, if they set one, or when the person is removed or leaves. The owner can see when each person last opened the program.
  • Leaving and removal. Anyone can leave a program shared with them, and the owner can remove anyone at any time. When someone leaves or is removed, their access ends and their own Flint conversations in that program are deleted. What they added to the program, such as comments, decision outcomes and changes, stays with it.
  • Handing a program over. The owner can hand a program over to someone it is already shared with, if that person has a Program Forgemaster plan. The new owner then controls the program as section 3 describes, and the previous owner stays on as a program manager.

6. Printing, downloads and export records

  • What can be printed or downloaded. You can print a steering committee pack or a closure report or save either as a PDF from your browser, and you can download the steering pack as a PowerPoint file. When deleting a program, the owner can also download its main registers as a CSV file. At any time, the owner can download all of a program’s data as one JSON file, with what Flint drafted, said or remembered in the program marked as AI-generated.
  • Who can. The owner and program and project managers can, except the download of all of a program’s data, which only the owner can make. Sponsors and viewers can only if the owner allows it for them; it is off unless the owner turns it on.
  • Export records. Every print and download is recorded with who made it, their name, email and role, what it was and when. The owner can see these records.
  • Watermarks. Copies made by anyone other than the owner show that person’s name, email address and the date on each page or slide.
  • Copies outside Program Forgemaster. Once a copy leaves Program Forgemaster, the person who made it is responsible for who they share it with, and section 8 of the Terms of Service applies: it may not be shared outside the Services except as the owner allows.

7. Comments and decisions

  • Comments. The owner, program and project managers and sponsors can comment on status reports, decisions, RAID items, roadmap items and benefits. Viewers can’t. Everyone who can see the program sees each comment and the name of the person who wrote it. Comments can’t be edited; the person who wrote one can delete it, and the owner can delete any comment. Deleting a record deletes its comments. Limits apply to how many comments one person can add in an hour and how many a program can hold.
  • Recording decisions. A sponsor, the owner or a program manager can record the outcome of a decision that is waiting: approved, rejected or need more information, with a note (a note is needed for “need more information”). Approving marks the decision as decided. The program’s history keeps every outcome recorded, with the name of the person who recorded it and when.
  • Alerts. Program Forgemaster flags problems such as roadmap items slipping past their baseline and risks overdue for review, using fixed rules on your program’s records and limits the owner or a program manager sets. No AI is used to find them, and they may miss things. Everyone who can see the program sees its alerts. The owner and program and project managers can dismiss an alert, giving a reason, which hides it for everyone until the records behind it change. Each dismissal and follow-up is recorded with the person’s name and role, the reason and when, and everyone who can see the program can see these records.

8. AI features

  • Flint. Program Forgemaster’s AI features are Flint, the AI program coach. Our AI page lists what Flint does and the information it uses. Section 6 of the Terms of Service applies to Flint’s output.
  • Flint’s drafts. Flint saves its drafts and suggested changes in your program, labeled as Flint drafts. They count for nothing and change nothing until a person approves them, and you can edit or discard them.
  • Red, amber and green. Flint never sets a red, amber or green status. The person writing a status report sets every status themselves.
  • Who uses Flint. Only the owner and program and project managers use Flint. Sponsors and viewers don’t use Flint and never see Flint’s drafts, Flint conversations or what Flint remembers. Each person’s Flint conversations are visible only to them. Only the owner and program managers can change or clear what Flint remembers about a program.
  • Allowances. Each Flint request counts toward a monthly allowance for the person who makes it, which resets at the start of each calendar month (UTC); on a shared program, each person uses their own allowance. Daily AI usage caps apply, for each person and for all of Program Forgemaster, along with a limit on how many Flint requests one person can have running at once, and we may pause Flint for everyone to protect the Services.

9. Reports

Use the “Report a problem” menu to report a bug or a service incident, and tick “Possible security issue” for a suspected Security Incident. Reports are visible only to you and our staff.

10. Deleting

  • Items and programs. People who can edit a record can delete it, such as benefits, projects, roadmap items, dependencies, RAID items, decisions, change requests, budget lines, benefit measurements and lessons learned. The owner can delete a whole program in Program Forgemaster, after typing its name to confirm, or can email info@vektorforgeai.com and we will delete it within 30 days. Deleting a program deletes it, with everything in it, for everyone it is shared with, and can’t be undone, so save any copies you need first (section 6). We keep a short record that the program was deleted, without its name or content, as our Privacy Policy describes.
  • Deleting your account. Deleting your VektorForgeAI account deletes the programs you own, for everyone they are shared with, and ends your access to programs other people shared with you. Your Flint conversations in those programs, and invitations still waiting for an answer that were sent to an email address Program Forgemaster already holds for your account, are deleted. What you added to other people’s programs, such as comments, decision outcomes, approvals and export records, stays with those programs but shows as “Former member” instead of your name and email. Our Privacy Policy describes this.