Has anyone written a charter for programming documents? Any advice and/or examples are welcome!

Programming documents have to be closely associated with specific tasks or implementations to be more effective, using real work examples to illustrate. Otherwise it would just be another programming guideline which is dry and bored and difficult to follow through.

We have used many different kinds of charters in our organization, for us, a charter essentially is a document that presents the idea, scope, and result of a potential project or program. In your case since you want to build this for programming documents, I guess the work is slightly scoped down as things that apply to a project management charter may not apply in entirety here. Still, I would suggest starting off with the following heads:

- Why (the need)
- What (the aim)
- How (the process)
- Who (the stakeholders)
- When (the timelines)

At a high level, a charter is defining the Who, What, When, Where and Why for a project or program.

Without understanding the specific need you have when you say programming documents, I would say focus on those areas and speak to them to understand what will fit for what you are trying to accomplish.

Most charters are the start of a project or phase which will formally authorize the existence of the need and how a team will solve that need.  Essentially establishing the objectives, high level scope, assumptions, deliverables, etc.  

Know your audience, most of the time the charter is to help the Executives see the business value of a specific project so you should keep that in mind as you are putting yours together.

Start with the executive summary, and then answer
 - Why
 - What
 - How
 - Budget
 - Deliverables
 - Risks / Assumptions

 - Timeline

I would suggest going to https://www.projectmanagement.com/ and you can find a lot of items and templates for the same.